Infrastructure/logto
0
Fork 0
mirror of https://github.com/logto-io/logto.git synced 2025-04-07 23:01:25 -05:00
Code Issues Activity

chore(console): rename OKTA to Okta (#5016)

Browse source 
* chore(console): rename OKTA to Okta

rename OKTA to Okta

* fix(console): fix build error

fix build error
This commit is contained in:
simeng-li 2023-12-01 10:14:46 +08:00 • committed by GitHub
parent 0acc49892a
commit d234c1483c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
packages/console/src/assets/docs/single-sign-on/AzureAD/README.mdx
View file

@ -66,7 +66,7 @@ Logto will fetch the metadata from the URL and configure the SAML SSO integratio
Logto provides a flexible way to map the user attributes returned from IdP to the user attributes in Logto. Logto will sync the following user attributes from IdP by default:
- id: The unique identifier of the user. Logto will read the `nameId` claim from the SAML response as the user id by default. You may leave this field as default unless you want to use a different claim.
- id: The unique identifier of the user. Logto will read the `nameId` claim from the SAML response as the user SSO identity id.
- email: The email address of the user. Logto will read the `email` claim from the SAML response as the user primary email by default.
- name: The name of the user.

8
packages/console/src/assets/docs/single-sign-on/OKTA/README.mdx
View file

@ -6,9 +6,9 @@ import applicationSettings from './assets/application_settings.webp';
import clientCredentials from './assets/client_credentials.webp';
import assignUsers from './assets/assign_users.webp';
<Step index={0} title="Create an OIDC application on OKTA admin portal">
<Step index={0} title="Create an OIDC application on Okta admin portal">
- Visit the OKTA admin portal and sign in as an administrator.
- Visit the Okta admin portal and sign in as an administrator.
- Navigate to the `Applications`/`Applications` page using the side menu.
- Click the `Create App Integration` button to create a new OIDC application.
- Select the `OIDC - OpenID Connect` option as the `Sign-in method`.
@ -30,7 +30,7 @@ Click the `Next` button to continue.
<OidcCallbackUri />
This is the URI that the OKTA will redirect the user's browser after successful authentication. After a user successfully authenticates with the IdP, the IdP redirects the user's browser back to this designated URI along with an authorization code. Logto will complete the authentication process based on authorization code received from this URI.
This is the URI that the Okta will redirect the user's browser after successful authentication. After a user successfully authenticates with the IdP, the IdP redirects the user's browser back to this designated URI along with an authorization code. Logto will complete the authentication process based on authorization code received from this URI.
<center>
<img src={applicationSettings} alt="application settings" />
@ -68,4 +68,4 @@ Users with email addresses in the specified domains will be restricted to use yo
</Step>
For more details about create OIDC integration with OKTA, please check [Create OIDC App Integrations](https://help.okta.com/oie/en-us/content/topics/apps/apps_app_integration_wizard_oidc.htm).
For more details about create OIDC integration with Okta, please check [Create OIDC App Integrations](https://help.okta.com/oie/en-us/content/topics/apps/apps_app_integration_wizard_oidc.htm).

6
packages/console/src/assets/docs/single-sign-on/SAML/README.mdx
View file

@ -39,12 +39,12 @@ With either of the above configurations, Logto will parse the IdP metadata and c
The user attributes returned from IdP may vary depending on the IdP configuration. Logto provides a flexible way to map the user attributes returned from IdP to the user attributes in Logto. You can configure the user attributes mapping in the SAML SSO integration experience tab.
For minimum configuration, please make sure the following attributes are well mapped either on the IdP side or Logto side:
- id: The unique identifier of the user. Logto will read the `nameId` claim from the SAML response as the user id by default. You may leave this field as default unless you want to use a different claim.
- id: The unique identifier of the user. Logto will read the `nameId` claim from the SAML response as the user SSO identity id.
- email: The email address of the user.
- name: The name of the user.
</Step>
<Step index={3} title="Set email domains and enable the SSO connector">