diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-10-18 12:13:41 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-10-18 12:13:41 +0000 |
| commit | 1e88fd9da8572e256a61f0307a5099653735730b (patch) | |
| tree | d3f2bf7ed543bfb38da0b9b1fe7508d02d3fd2e9 /doc/administration/auth/oidc.md | |
| parent | f047727bf270fc9a64e3420a0c23760962b38f14 (diff) | |
| download | gitlab-ce-1e88fd9da8572e256a61f0307a5099653735730b.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/auth/oidc.md')
| -rw-r--r-- | doc/administration/auth/oidc.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/administration/auth/oidc.md b/doc/administration/auth/oidc.md index 6a037e75f54..12729f2050b 100644 --- a/doc/administration/auth/oidc.md +++ b/doc/administration/auth/oidc.md @@ -228,8 +228,7 @@ Azure B2C [offers two ways of defining the business logic for logging in a user] While cumbersome to configure, custom policies are required because standard Azure B2C user flows [do not send the OpenID `email` claim](https://github.com/MicrosoftDocs/azure-docs/issues/16566). In -other words, they do not work with the [`allow_single_sign_on` or `auto_link_user` -parameters](../../integration/omniauth.md#initial-omniauth-configuration). +other words, they do not work with the [`allow_single_sign_on` or `auto_link_user` parameters](../../integration/omniauth.md#initial-omniauth-configuration). With a standard Azure B2C policy, GitLab cannot create a new account or link to an existing one with an email address. |