-
Notifications
You must be signed in to change notification settings - Fork 710
Add TiDB Dashboard session docs (#6058) #6062
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
ti-chi-bot
merged 4 commits into
pingcap:release-5.0
from
ti-chi-bot:cherry-pick-6058-to-release-5.0
Sep 29, 2021
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,56 @@ | ||
| --- | ||
| title: Share TiDB Dashboard Sessions | ||
| summary: Learn how to share the current TiDB Dashboard session to other users. | ||
| --- | ||
|
|
||
| # Share TiDB Dashboard Sessions | ||
|
|
||
| You can share the current session of the TiDB Dashboard to other users so that they can access and operate the TiDB Dashboard without entering the user password. | ||
|
|
||
| ## Steps for the Inviter | ||
|
|
||
| 1. Sign into TiDB Dashboard. | ||
|
|
||
| 2. Click the username in the left sidebar to access the configuration page. | ||
|
|
||
| 3. Click **Share Current Session**. | ||
|
|
||
|  | ||
|
|
||
| > **Note:** | ||
| > | ||
| > For security reasons, the shared session cannot be shared again. | ||
|
|
||
| 4. Adjust sharing settings in the popup dialog: | ||
|
|
||
| - Expire in: How long the shared session will be effective. Signing out of the current session does not affect the effective time of the shared session. | ||
|
|
||
| - Share as read-only privilege: The shared session only permits read operations but not write operations (such as modifying configurations). This feature is available only in v5.0.4 or a later version. | ||
|
|
||
| 5. Click **Generate Authorization Code**. | ||
|
|
||
|  | ||
|
|
||
| 6. Provide the generated **Authorization Code** to the user to whom you want to share the session. | ||
|
|
||
|  | ||
|
|
||
| > **Warning:** | ||
| > | ||
| > Keep your authorization code secure and do not send it to anyone who is untrusted. Otherwise, they will be able to access and operate TiDB Dashboard without your authorization. | ||
|
|
||
| ## Steps for the Invitee | ||
|
|
||
| 1. On the sign-in page of TiDB Dashboard, click **Use Alternative Authentication**. | ||
|
|
||
|  | ||
|
|
||
| 2. Click **Authorization Code** to use it to sign in. | ||
|
|
||
|  | ||
|
|
||
| 3. Enter the authorization code you have received from the inviter. | ||
|
|
||
| 4. Click **Sign In**. | ||
|
|
||
|  |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,155 @@ | ||
| --- | ||
| title: Configure SSO for TiDB Dashboard | ||
| summary: Learn how to enable SSO to sign into TiDB Dashboard. | ||
| --- | ||
|
|
||
| # Configure SSO for TiDB Dashboard | ||
|
|
||
| TiDB Dashboard supports [OIDC](https://openid.net/connect/)-based Single Sign-On (SSO). After enabling the SSO feature of TiDB Dashboard, the configured SSO service is used for your sign-in authentication and then you can access TiDB Dashboard without entering the SQL user password. | ||
|
|
||
| ## Configure OIDC SSO | ||
|
|
||
| > **Note:** | ||
| > | ||
| > This feature is available only in v5.0.4 or a later version. | ||
|
|
||
| ### Enable SSO | ||
|
|
||
| 1. Sign into TiDB Dashboard. | ||
|
|
||
| 2. Click the username in the left sidebar to access the configuration page. | ||
|
|
||
| 3. In the **Single Sign-On** section, select **Enable to use SSO when sign into TiDB Dashboard**. | ||
|
|
||
| 4. Fill the **OIDC Client ID** and the **OIDC Discovery URL** fields in the form. | ||
|
|
||
| Generally, you can obtain the two fields from the SSO service provider: | ||
|
|
||
| - OIDC Client ID is also called OIDC Token Issuer. | ||
| - OIDC Discovery URL is also called OIDC Token Audience. | ||
|
|
||
| 5. Click **Authorize Impersonation** and input the SQL password. | ||
|
|
||
| TiDB Dashboard will store this SQL password and use it to impersonate a normal SQL sign-in after an SSO sign-in is finished. | ||
|
|
||
|  | ||
|
|
||
| > **Note:** | ||
| > | ||
| > The password you have entered will be encrypted and stored. The SSO sign-in will fail after the password of the SQL user is changed. In this case, you can re-enter the password to bring SSO back. | ||
|
|
||
| 6. Click **Authorize and Save**. | ||
|
|
||
|  | ||
|
|
||
| 7. Click **Update** (Update) to save the configuration. | ||
|
|
||
|  | ||
|
|
||
| Now SSO sign-in has been enabled for TiDB Dashboard. | ||
|
|
||
| > **Note:** | ||
| > | ||
| > For security reasons, some SSO services require additional configuration for the SSO service, such as the trusted sign-in and sign-out URIs. Refer to the documentation of the SSO service for further information. | ||
|
|
||
| ### Disable SSO | ||
|
|
||
| You can disable the SSO, which will completely erase the stored SQL password: | ||
|
|
||
| 1. Sign into TiDB Dashboard. | ||
|
|
||
| 2. Click the username in the left sidebar to access the configuration page. | ||
|
|
||
| 3. In the **Single Sign-On** section, deselect **Enable to use SSO when sign into TiDB Dashboard**. | ||
|
|
||
| 4. Click **Update** (Update) to save the configuration. | ||
|
|
||
|  | ||
|
|
||
| ### Re-enter the password after a password change | ||
|
|
||
| The SSO sign-in will fail once the password of the SQL user is changed. In this case, you can bring back the SSO sign-in by re-entering the SQL password: | ||
|
|
||
| 1. Sign into TiDB Dashboard. | ||
|
|
||
| 2. Click the username in the left sidebar to access the configuration page. | ||
|
|
||
| 3. In the **Single Sign-On** section, Click **Authorize Impersonation** and input the updated SQL password. | ||
|
|
||
|  | ||
|
|
||
| 4. Click **Authorize and Save**. | ||
|
|
||
| ## Sign in via SSO | ||
|
|
||
| Once SSO is configured for TiDB Dashboard, you can sign in via SSO by taking following steps: | ||
|
|
||
| 1. In the sign-in page of TiDB Dashboard, click **Sign in via Company Account**. | ||
|
|
||
|  | ||
|
|
||
| 2. Sign into the system with SSO service configured. | ||
|
|
||
| 3. You are redirected back to TiDB Dashboard to finish the sign-in. | ||
|
|
||
| ## Example: Use Okta for TiDB Dashboard SSO sign-in | ||
|
|
||
| [Okta](https://www.okta.com/) is an OIDC SSO identity service, which is compatible with the SSO feature of TiDB Dashboard. The steps below demonstrate how to configure Okta and TiDB Dashboard so that Okta can be used as the TiDB Dashboard SSO provider. | ||
|
|
||
| ### Step 1: Configure Okta | ||
|
|
||
| First, create an Okta Application Integration to integrate SSO. | ||
|
|
||
| 1. Access the Okta administration site. | ||
|
|
||
| 2. Navigate from the left sidebar **Applications** > **Applications**. | ||
|
|
||
| 3. Click **Create App Integration**。 | ||
|
|
||
|  | ||
|
|
||
| 4. In the poped up dialog, choose **OIDC - OpenID Connect** in **Sign-in method**. | ||
|
|
||
| 5. Choose **Single-Page Application** in **Application Type**. | ||
|
|
||
| 6. Click the **Next** button. | ||
|
|
||
|  | ||
|
|
||
| 7. Fill **Sign-in redirect URIs** as follows: | ||
|
|
||
| ``` | ||
| http://DASHBOARD_IP:PORT/dashboard/?sso_callback=1 | ||
| ``` | ||
|
|
||
| Substitute `DASHBOARD_IP:PORT` with the actual domain (or IP address) and port that you use to access the TiDB Dashboard in the browser. | ||
|
|
||
| 8. Fill **Sign-out redirect URIs** as follows: | ||
|
|
||
| ``` | ||
| http://DASHBOARD_IP:PORT/dashboard/ | ||
| ``` | ||
|
|
||
| Similarly, substitute `DASHBOARD_IP:PORT` with the actual domain (or IP address) and port. | ||
|
|
||
|  | ||
|
|
||
| 9. Configure what type of users in your organization is allowed for SSO sign-in in the **Assignments** field, and then click **Save** to save the configuration. | ||
|
|
||
|  | ||
|
|
||
| ### Step 2: Obtain OIDC information and fill in TiDB Dashboard | ||
|
|
||
| 1. In the Application Integration just created in Okta, click **Sign On**. | ||
|
|
||
|  | ||
|
|
||
| 2. Copy values of the **Issuer** and **Audience** fields from the **OpenID Connect ID Token** section. | ||
|
|
||
|  | ||
|
|
||
| 3. Open the TiDB Dashboard configuration page, fill **OIDC Client ID** with **Issuer** obtained from the last step and fill **OIDC Discovery URL** with **Audience**. Then finish the authorization and save the configuration. For example: | ||
|
|
||
|  | ||
|
|
||
| Now TiDB Dashboard has been configured to use Okta SSO for sign-in. | ||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.