Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This PR modifies files in the 'clerk-typedoc/' folder. These files are auto-generated from the clerk/javascript repository and should not be edited directly. To make changes to TypeDoc documentation:
Thanks for contributing! 🙏 |
| @@ -0,0 +1,7 @@ | |||
| --- | |||
| title: '`OAuthConsentInfo`' | |||
| description: An interface that represents OAuth consent information. | |||
There was a problem hiding this comment.
Was this added due to a bad git rebase?
| sdk: astro, nextjs, react, tanstack-react-start, vue, js-frontend | ||
| --- | ||
|
|
||
| The `<ConfigureSSO />` component renders a guided wizard that lets a signed-in user — typically the IT admin at one of your enterprise customers — configure an enterprise SSO connection end-to-end without leaving your application or touching the Clerk Dashboard. |
There was a problem hiding this comment.
Let's add an screenshot of the component once we release it
| <If sdk="astro"> | ||
| ```astro {{ filename: 'src/pages/sso-setup.astro' }} | ||
| --- | ||
| import { __experimental_ConfigureSSO as ConfigureSSO } from '@clerk/astro/components' |
There was a problem hiding this comment.
We'll remove the __experimental prefix from here before releasing it GA - this is just used in the SDK now so we can incrementally implement internally
|
|
||
| 1. In the Okta dashboard, find the **Attribute Statements (optional)** section. | ||
| 1. For the **Name** field, enter `mail`. | ||
| 1. For the **Value** field, choose `user.email` from the dropdown. | ||
| 1. Select the **Add Another** button to add another attribute. | ||
| 1. For the **Name** field, enter `firstName`. | ||
| 1. For the **Value** field, choose `user.firstName` from the dropdown. | ||
| 1. Select the **Add Another** button to add another attribute. | ||
| 1. For the **Name** field, enter `lastName`. | ||
| 1. For the **Value** field, choose `user.lastName` from the dropdown. | ||
| 1. Scroll to the bottom of the page and select the **Next** button to continue. | ||
| 1. You will be redirected to the **Feedback** page. Fill out the feedback however you would like and select the **Finish** button to complete the setup. | ||
| | Attribute | Required | Claim name | | ||
| | - | - | - | | ||
| | Email address | ✅ | `user.email` | | ||
| | First name | ❌ | `user.firstName` | | ||
| | Last name | ❌ | `user.lastName` | | ||
|
|
||
| Okta uses these values by default, so you probably won't need to configure them manually. However, incorrect attribute mappings cause many SAML configuration errors. If the integration doesn't work as expected, define the attributes explicitly: | ||
|
|
||
| 1. In the Okta dashboard, find the **Attribute Statements** section. | ||
| 1. Select **Add expression** for each attribute, and enter the following name and expression pairs: | ||
| - `mail` and `user.profile.email` |
There was a problem hiding this comment.
Was this due to the Okta UI changes? They recently updated the UI for attribute statements and our copy here was using the "legacy" UI
There was a problem hiding this comment.
yep, this is the new ui changes. using expressions instead of legacy ui
There was a problem hiding this comment.
we should also update self-serve sso to use these instructions too 👀
Co-authored-by: Laura Beatris <48022589+LauraBeatris@users.noreply.github.com>
🔎 Previews:
<ConfigureSSO/>What does this solve? What changed?
<ConfigureSSO/>so folks can embed this component to enable this feature.Deadline
Other resources