feat: add Requesting App to XAA docs#1465
Conversation
lrzhou25
added
main-docs
Summary
Errors per inputErrors in main/docs/secure/call-apis-on-users-behalf/xaa/idp/okta-as-oidc-idp.mdx
|
f9bc906 to
af0477b
Compare
| &connection=<YOUR_OKTA_WORKFORCE_CONNECTION_NAME> | ||
| ``` | ||
|
|
||
| When the login completes, Auth0 returns an authorization code to your callback URL. Exchange it for tokens at the Auth0 `/token` endpoint. Auth0 returns an access token, ID token, and refresh token issued by your Auth0 tenant. The Okta tokens are stored internally in Token Vault. |
There was a problem hiding this comment.
Is it worth adding an example of the request to get the refresh token here?
There was a problem hiding this comment.
would you happen to have one?
|
|
||
| Use this approach to test the raw XAA protocol steps, or if you have not configured Token Vault. | ||
|
|
||
| ### Log in to the Requesting App |
There was a problem hiding this comment.
This section reads as though we should be requesting an id token from auth0, but actually we need to complete the login flow for the okta tenant. Could that be more clear? Maybe that's not the case, it's just the impression I get when reading it
| You also need access to a Resource App Auth0 tenant. To set one up, read [Set Up Resource App](/docs/secure/call-apis-on-users-behalf/xaa/idp/okta-as-oidc-idp). From the Resource App tenant, you need: | ||
|
|
||
| - The Resource App tenant's issuer URL. For example, `https://<RESOURCE_APP_TENANT>.auth0.com/` | ||
| - A Client ID and Client Secret for the Requesting App registered in the Resource App tenant |
There was a problem hiding this comment.
The wording here is a bit confusing, is it correct where we say "Requesting App registered in the Resource App tenant"?
| @@ -0,0 +1,168 @@ | |||
| --- | |||
There was a problem hiding this comment.
I find it a bit odd that we have a section for idp integration, and this document is placed in a "idp agnostic" place but it's very Okta specific. Is it worth moving it somewhere else?
| 2. Under Sign On, select Edit and add your **Auth0 Tenant’s callback URL** in the **Redirect URI** field. | ||
| 3. Select Save. | ||
|
|
||
| <Frame></Frame> |
There was a problem hiding this comment.
Are these docs using a single tenant in auth0 for the requesting and resource apps? I'm asking because the new page set-up-requesting-app.mdx seems to reference 2 tenants, in this page I can see the same tenant being used for both in the pictures
2 participants
Description
References
Testing
Checklist
CONTRIBUTING.md.