|
|
@ -191,7 +191,7 @@ In the ca.json configuration file, a complete JWK provisioner example looks like
|
|
|
|
### OIDC
|
|
|
|
### OIDC
|
|
|
|
|
|
|
|
|
|
|
|
An OIDC provisioner allows a user to get a certificate after authenticating
|
|
|
|
An OIDC provisioner allows a user to get a certificate after authenticating
|
|
|
|
himself with an OAuth OpenID Connect identity provider. The ID token provided
|
|
|
|
with an OAuth OpenID Connect identity provider. The ID token provided
|
|
|
|
will be used on the CA authentication, and by default, the certificate will only
|
|
|
|
will be used on the CA authentication, and by default, the certificate will only
|
|
|
|
have the user's email as a Subject Alternative Name (SAN) Extension.
|
|
|
|
have the user's email as a Subject Alternative Name (SAN) Extension.
|
|
|
|
|
|
|
|
|
|
|
|