Skip to content

Commit cb802d2

Browse files
authored
Merge pull request #25147 from timhughes/patch-1
Updates links to Dex
2 parents 27ca111 + f5132af commit cb802d2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/en/docs/reference/access-authn-authz/authentication.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -354,7 +354,7 @@ tokens on behalf of another.
354354
Kubernetes does not provide an OpenID Connect Identity Provider.
355355
You can use an existing public OpenID Connect Identity Provider (such as Google, or
356356
[others](https://connect2id.com/products/nimbus-oauth-openid-connect-sdk/openid-connect-providers)).
357-
Or, you can run your own Identity Provider, such as CoreOS [dex](https://github.com/coreos/dex),
357+
Or, you can run your own Identity Provider, such as [dex](https://dexidp.io/),
358358
[Keycloak](https://github.com/keycloak/keycloak),
359359
CloudFoundry [UAA](https://github.com/cloudfoundry/uaa), or
360360
Tremolo Security's [OpenUnison](https://github.com/tremolosecurity/openunison).
@@ -365,7 +365,7 @@ For an identity provider to work with Kubernetes it must:
365365
2. Run in TLS with non-obsolete ciphers
366366
3. Have a CA signed certificate (even if the CA is not a commercial CA or is self signed)
367367

368-
A note about requirement #3 above, requiring a CA signed certificate. If you deploy your own identity provider (as opposed to one of the cloud providers like Google or Microsoft) you MUST have your identity provider's web server certificate signed by a certificate with the `CA` flag set to `TRUE`, even if it is self signed. This is due to GoLang's TLS client implementation being very strict to the standards around certificate validation. If you don't have a CA handy, you can use [this script](https://github.com/coreos/dex/blob/1ee5920c54f5926d6468d2607c728b71cfe98092/examples/k8s/gencert.sh) from the CoreOS team to create a simple CA and a signed certificate and key pair.
368+
A note about requirement #3 above, requiring a CA signed certificate. If you deploy your own identity provider (as opposed to one of the cloud providers like Google or Microsoft) you MUST have your identity provider's web server certificate signed by a certificate with the `CA` flag set to `TRUE`, even if it is self signed. This is due to GoLang's TLS client implementation being very strict to the standards around certificate validation. If you don't have a CA handy, you can use [this script](https://github.com/dexidp/dex/blob/master/examples/k8s/gencert.sh) from the Dex team to create a simple CA and a signed certificate and key pair.
369369
Or you can use [this similar script](https://raw.githubusercontent.com/TremoloSecurity/openunison-qs-kubernetes/master/src/main/bash/makessl.sh) that generates SHA256 certs with a longer life and larger key size.
370370

371371
Setup instructions for specific systems:

0 commit comments

Comments
 (0)