feat: add azure oidc PKI auth instead of client secret (#9054)

* feat: add azure oidc PKI auth instead of client secret
* add client cert and key as deployment options
* Custom token refresher to handle pki auth
This commit is contained in:
Steven Masley
2023-08-14 17:33:13 -05:00
committed by GitHub
parent 4e36f91ea2
commit 25ce30df36
13 changed files with 748 additions and 35 deletions
+20
View File
@@ -418,6 +418,16 @@ Whether new users can sign up with OIDC.
OIDC auth URL parameters to pass to the upstream provider.
### --oidc-client-cert-file
| | |
| ----------- | ----------------------------------------- |
| Type | <code>string</code> |
| Environment | <code>$CODER_OIDC_CLIENT_CERT_FILE</code> |
| YAML | <code>oidc.oidcClientCertFile</code> |
Pem encoded certificate file to use for oauth2 PKI/JWT authorization. The public certificate that accompanies oidc-client-key-file. A standard x509 certificate is expected.
### --oidc-client-id
| | |
@@ -428,6 +438,16 @@ OIDC auth URL parameters to pass to the upstream provider.
Client ID to use for Login with OIDC.
### --oidc-client-key-file
| | |
| ----------- | ---------------------------------------- |
| Type | <code>string</code> |
| Environment | <code>$CODER_OIDC_CLIENT_KEY_FILE</code> |
| YAML | <code>oidc.oidcClientKeyFile</code> |
Pem encoded RSA private key to use for oauth2 PKI/JWT authorization. This can be used instead of oidc-client-secret if your IDP supports it.
### --oidc-client-secret
| | |