You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
attestation-service: make challenge signing key path configurable
The RSA private key used to sign and verify attestation challenge (nonce)
tokens was hard-coded to
`/etc/trustee/attestation-service/nonce_token_issuer/key.pem`, so deployments
had no way to relocate it (e.g. onto a mounted secret volume).
Add an optional `challenge_key_path` field to the AS `Config`. When it is
unset the previous default path is used and the key is still generated on
first use, so existing deployments are unaffected. The challenge generation
and verification helpers now take the resolved path as a parameter, threaded
through from the config by both the RESTful and gRPC front-ends.
Signed-off-by: Jiale Zhang <zhangjiale@linux.alibaba.com>
Copy file name to clipboardExpand all lines: attestation-service/docs/config.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,7 @@ section:
18
18
|`work_dir`| String | The location for Attestation Service to store data. | False | Firstly try to read from ENV `AS_WORK_DIR`. If not any, use `/opt/confidential-containers/attestation-service`|
|`attestation_token_broker`|[AttestationTokeBroker][1]| Attestation result token configuration. | False | - |
21
+
|`challenge_key_path`| String | Path to the RSA private key (PEM) used to sign and verify attestation challenge (nonce) tokens. The key is generated on first use if the file does not exist. | False |`/etc/trustee/attestation-service/nonce_token_issuer/key.pem`|
0 commit comments