*: Add use Auth0 as example to login dashboard by sso#7093
Conversation
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
3f46c4b to
319ca1d
Compare
breezewish
left a comment
There was a problem hiding this comment.
Generally looks great! This is a good supplyment!
|
|
||
| ### 步骤二:获取 TiDB Dashboard 所需的配置参数并填入 TiDB Dashboard | ||
|
|
||
| 1. 将 Auth0 **Settings** 栏 **Basic Information** 项的 **Client ID** 字段的值填入 TiDB Dashboard 的 **OIDC Client ID**,将 **Domain** 字段的值,加上 `https://` 前缀和 `/` 后缀后填入 **OIDC Discovery URL** 中。完成授权并保存配置即可。 |
There was a problem hiding this comment.
I guess the / suffix is optional. I'm not sure. You may have a try :)
There was a problem hiding this comment.
I have tried, miss the / will report an error, maybe we can add it automatically? but maybe okta doesn't need to end with /, let me check.
There was a problem hiding this comment.
Yep, auth0 needs but okta doesn't need.
There was a problem hiding this comment.
It's a wired behaviour. Maybe we should revisit the implementation.
There was a problem hiding this comment.
ok, let me check.
Change the link for Auth0 from www.okta.com to auth0.com.
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 2b829ad |
|
In response to a cherrypick label: new pull request created: #7130. |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
|
In response to a cherrypick label: new pull request created: #7131. |
|
In response to a cherrypick label: new pull request created: #7132. |
|
In response to a cherrypick label: new pull request created: #7133. |
What is changed, added or deleted? (Required)
Add use Auth0 as a new example to login TiDB Dashboard by SSO.
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?