From bc5ad4251202c765d0d239c31ea62dd20e50b9cf Mon Sep 17 00:00:00 2001 From: Iliana Panagopoulou Date: Wed, 29 Jul 2020 12:11:07 +0300 Subject: [PATCH] Fix "connectors" table formatting --- Home.md | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/Home.md b/Home.md index 4e6423d..e85b545 100644 --- a/Home.md +++ b/Home.md @@ -29,16 +29,18 @@ A "connector" is a strategy used by dex for authenticating a user against anothe Depending on the connectors limitations in protocols can prevent dex from issuing refresh tokens or returning group membership claims. For example, because SAML doesn't provide a non-interactive way to refresh assertions, if a user logs in through the SAML connector dex won't issue a refresh token to its client. Refresh token support is required for clients that require offline access, such as kubectl. Dex implements the following connectors: -Name supports refresh tokens supports groups claim status notes -LDAP yes yes stable -GitHub yes yes stable -SAML 2.0 no yes stable -GitLab yes yes beta -OpenID Connect yes no (#1065) beta Includes Google, Salesforce, Azure, etc. -LinkedIn yes no beta -Microsoft yes yes beta -AuthProxy no no alpha Authentication proxies such as Apache2 mod_auth, etc. -Bitbucket Cloud yes yes alpha + +| Name |supports refresh tokens |supports groups claim |status |notes| +| :------------- |:-------------:| :-----:|:-----:|:-------------------:| +| LDAP | yes | yes | stable || +| GitHub | yes | yes | stable || +| SAML 2.0 | no |yes | stable || +| GitLab | yes |yes | beta || +| OpenID Connect |yes | no (#1065) | beta | Includes Google, Salesforce, Azure, etc.| +| LinkedIn | yes | no | beta || +| Microsoft | yes | yes |beta || +| AuthProxy | no |no |alpha |Authentication proxies such as Apache2 mod_auth, etc.| +| Bitbucket Cloud | yes | yes | alpha || **Stable, beta, and alpha are defined as:**