docs(sso) move root user warning to earlier in SSO guides (#7028)

This commit is contained in:
Maggie Hays 2023-01-12 18:37:22 -06:00 committed by GitHub
parent 7c60659307
commit 8e920717aa
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 29 additions and 8 deletions

View File

@ -6,6 +6,13 @@ delegate authentication responsibility to identity providers like Microsoft Azur
This guide will provide steps for configuring DataHub authentication using Microsoft Azure.
:::caution
Even when OIDC is configured, the root user can still login without OIDC by going
to `/login` URL endpoint. It is recommended that you don't use the default
credentials by mounting a different file in the front end container. To do this
please see [this guide](../jaas.md) to mount a custom user.props file for a JAAS authenticated deployment.
:::
## Steps
### 1. Create an application registration in Microsoft Azure portal

View File

@ -6,6 +6,13 @@ authentication responsibility to identity providers like Google.
This guide will provide steps for configuring DataHub authentication using Google.
:::caution
Even when OIDC is configured, the root user can still login without OIDC by going
to `/login` URL endpoint. It is recommended that you don't use the default
credentials by mounting a different file in the front end container. To do this
please see [this guide](../jaas.md) to mount a custom user.props file for a JAAS authenticated deployment.
:::
## Steps
### 1. Create a project in the Google API Console

View File

@ -6,6 +6,13 @@ delegate authentication responsibility to identity providers like Okta.
This guide will provide steps for configuring DataHub authentication using Okta.
:::caution
Even when OIDC is configured, the root user can still login without OIDC by going
to `/login` URL endpoint. It is recommended that you don't use the default
credentials by mounting a different file in the front end container. To do this
please see [this guide](../jaas.md) to mount a custom user.props file for a JAAS authenticated deployment.
:::
## Steps
### 1. Create an application in Okta Developer Console

View File

@ -6,6 +6,13 @@ This enables operators of DataHub to integrate with 3rd party identity providers
When configured, OIDC auth will be enabled between clients of the DataHub UI & `datahub-frontend` server. Beyond this point is considered
to be a secure environment and as such authentication is validated & enforced only at the "front door" inside datahub-frontend.
:::caution
Even if OIDC is configured the root user can still login without OIDC by going
to `/login` URL endpoint. It is recommended that you don't use the default
credentials by mounting a different file in the front end container. To do this
please see [this guide](../jaas.md) to mount a custom user.props file for a JAAS authenticated deployment.
:::
## Provider-Specific Guides
1. [Configuring OIDC using Google](configure-oidc-react-google.md)
@ -181,11 +188,4 @@ A brief summary of the steps that occur when the user navigates to the React app
can be used to retrieve information on behalf of the authenticated user
6. DataHub fetches the authenticated user's profile and extracts a username to identify the user on DataHub (eg. urn:li:corpuser:username)
7. DataHub sets session cookies for the newly authenticated user
8. DataHub redirects the user to the homepage ("/")
### Root user
Even if OIDC is configured the root user can still login without OIDC by going
to `/login` URL endpoint. It is recommended that you don't use the default
credentials by mounting a different file in the front end container. To do this
please see how to mount a custom user.props file for a JAAS authenticated deployment.
8. DataHub redirects the user to the homepage ("/")