diff --git a/docs/integrate-logto/third-party-applications/README.mdx b/docs/integrate-logto/third-party-applications/README.mdx index 42f58ec4efe..339dbe5a0a7 100644 --- a/docs/integrate-logto/third-party-applications/README.mdx +++ b/docs/integrate-logto/third-party-applications/README.mdx @@ -12,7 +12,7 @@ Logto's third-party application integration enables you to leverage Logto as an An Identity Provider (IdP) is a service that verifies user identities and manages their login credentials. After confirming a user's identity, the IdP generates authentication tokens or assertions and allows the user to access various applications or services without needing to log in again. -Unlike the applications you created in the [Integrate Logto into your application](/integrate-logto/integrate-logto-into-your-application) guide that are developed and fully controlled by you, third-party applications are independent services developed by external developers or business partners. +Unlike the applications you created in the [Integrate Logto into your application](/integrate-logto/integrate-logto-into-your-application) guide that are developed and fully controlled by you, third-party applications are independent services developed by external developers or business partners. When users sign in to a third-party application via Logto (e.g., by clicking "Sign in with Logto"), they will be presented with a [consent screen](/end-user-flows/consent-screen) asking them to review and authorize the requested user and organization permissions before access is granted. This integration approach is well-suited for common business scenarios. You can enable users to access partner applications using their Logto accounts, just like how enterprise users sign in to Slack with Google Workspace. You can also build an open platform where third-party applications can add "Sign in with Logto" functionality, similar to "Sign in with Google." @@ -20,43 +20,34 @@ Logto is an identity service built on the [OpenID Connect (OIDC)](https://auth.w Thus due to OIDC builds upon [OAuth 2.0](https://auth.wiki/oauth-2.0) adding an authentication layer, you can also integrate third-party app using OAuth protocol. -## Create an third-party application in Logto \{#create-an-third-party-application-in-logto} +## Create a third-party application in Logto \{#create-a-third-party-application-in-logto} 1. Go to Console > Applications. -2. Click on the "Create application" button. Select "Third-party app" as the application type and choose one of the following integration protocols: - - OIDC / OAuth +2. Click on the "Create application" button. Select "**Third-party app**" as the application type, then choose one of the following integration options based on your application architecture: + - **Traditional web app**: For server-side web applications that can securely store client secrets. This is the most common type for third-party integrations, such as enterprise SaaS platforms or partner portals that handle authentication on the server side. + - **Single page app (SPA)**: For client-side web applications that run entirely in the user's browser and cannot securely store client secrets. In this scenario, the client obtains tokens directly from the authorization server without going through a backend. A typical example is MCP (Model Context Protocol) integrations, where the MCP Client initiates authentication directly with the auth server to access various MCP Servers—the MCP Server providers don't control the client applications. + - **Native app**: For mobile or desktop applications that run on user devices and cannot securely store client secrets. Examples include desktop applications like Claude Desktop or VS Code that need to authenticate users to access third-party services. 3. Enter a name and description for your application and click on the “Create” button. A new third-party application will be created. All created third-party applications will be catalogued on the Applications page under the "Third-party apps" tab. This arrangement helps you distinguish them from your own applications, making it easier to manage all your applications in one place. -## Set up the OIDC configurations \{#set-up-the-oidc-configurations} - -:::note -Before setting up the OIDC configurations, please ensure you've [created an OIDC third-party application](/quick-starts/third-party-oidc). -::: +## Set up the OIDC / OAuth configurations \{#set-up-the-oidc-configurations} 1. Provide the [**redirect URI**](/integrate-logto/application-data-structure#redirect-uris) of your OIDC third-party application. This is the URL that the third-party application will redirect users to after they are authenticated by Logto. You can usually find this information in the third-party application's IdP connection settings page. -2. Retrieve the [**client ID**](/integrate-logto/application-data-structure#application-id) and [**client secret**](/integrate-logto/application-data-structure#application-secret) from Logto application details page and enter them into your service provider's IdP connection settings page. +2. Retrieve the [**client ID**](/integrate-logto/application-data-structure#application-id) from Logto application details page and enter it into your service provider's IdP connection settings page. + + - For **traditional web apps**, also retrieve the [**client secret**](/integrate-logto/application-data-structure#application-secret) and provide it to your service provider, as server-side applications can securely store secrets. + - For **single page apps (SPA)** and **native apps**, client secret is not required since these applications cannot securely store secrets. They use [PKCE (Proof Key for Code Exchange)](https://auth.wiki/pkce) for secure authorization instead. 3. Retrieve the [**authorization endpoint**](/integrate-logto/application-data-structure#authorization-endpoint) and [**token endpoint**](/integrate-logto/application-data-structure#token-endpoint) from Logto application details page and provide them to your service provider. - If your service provider supports OIDC discovery, you can simply copy the **discovery endpoint** from Logto application details page and provide it to your service provider. The service provider will be able to retrieve all the up to date OIDC authentication information from the discovery endpoint automatically. + If your service provider supports OIDC discovery, you can simply copy the **discovery endpoint** from Logto application details page and provide it to your service provider. The service provider will be able to retrieve all the up-to-date OIDC authentication information from the discovery endpoint automatically. Otherwise, click on the **Show endpoint details** button to view all the OIDC authentication endpoints. -## Consent screen for OIDC third-party applications \{#consent-screen-for-oidc-third-party-applications} - -For security reasons, all the OIDC third-party applications will be redirected to a [consent screen](/end-user-flows/consent-screen) for user authorization after they are authenticated by Logto. - -All the third-party requested [user profile permissions](/integrate-logto/third-party-applications/permission-management#user-permissions-user-profile-scopes), [API resource scopes](/integrate-logto/third-party-applications/permission-management#api-resource-permissions-api-resource-scopes), [organization permissions](/integrate-logto/third-party-applications/permission-management#organization-permissions-organization-scopes), and organization membership information will be displayed on the consent screen. - -These requested permissions will be granted to the third-party applications only after the user clicks on the "Authorize" button. - -
- consent screen -
+## Manage permissions and branding \{#manage-permissions-and-branding} -## Further actions \{#further-actions} +Once the OIDC configurations are set up, you can manage what permissions the third-party application can request and customize the branding of the consent screen: +## Consent screen for third-party applications \{#consent-screen-for-third-party-applications} + +For security reasons, all the OIDC third-party applications will be redirected to a [consent screen](/end-user-flows/consent-screen) for user authorization after they are authenticated by Logto. + +All the third-party requested [user profile permissions](/integrate-logto/third-party-applications/permission-management#user-permissions-user-profile-scopes), [API resource scopes](/integrate-logto/third-party-applications/permission-management#api-resource-permissions-api-resource-scopes), [organization permissions](/integrate-logto/third-party-applications/permission-management#organization-permissions-organization-scopes), and organization membership information will be displayed on the consent screen. + +These requested permissions will be granted to the third-party applications only after the user clicks on the "Authorize" button. + +
+ consent screen +
+ ## FAQs \{#faqs}
diff --git a/docs/quick-starts/third-party/_quick-starts-reference.md b/docs/quick-starts/third-party/_quick-starts-reference.md new file mode 100644 index 00000000000..7b0b002e1ae --- /dev/null +++ b/docs/quick-starts/third-party/_quick-starts-reference.md @@ -0,0 +1,10 @@ +Under the hood, a third-party app is just a standard OAuth 2.0 / OIDC client. This means you (or the third-party developer) can use any OAuth 2.0 / OIDC library or framework to integrate with Logto. + +If you're not familiar with OAuth 2.0 or OIDC, you can start by following one of our quick start guides based on your application type. + +A few things to keep in mind: + +1. Most of our quick start guides are written for first-party apps, but you can still use them as a reference for third-party app integration. +2. The main difference is that third-party apps will show a consent screen, asking users for explicit permission to access their data. + +You can find more information in our [quick start guides](/quick-starts). diff --git a/docs/quick-starts/third-party/native/README.mdx b/docs/quick-starts/third-party/native/README.mdx new file mode 100644 index 00000000000..6d3774060a6 --- /dev/null +++ b/docs/quick-starts/third-party/native/README.mdx @@ -0,0 +1,85 @@ +--- +slug: /quick-starts/third-party-native +sidebar_label: Third-party app (Native app) +sidebar_custom_props: + description: Integrate a third-party native (mobile/desktop) application using OIDC / OAuth protocol with PKCE. + logoFilename: 'native.svg' +--- + +import AuthorizationIcon from '@site/src/assets/authorization.svg'; +import CustomizationIcon from '@site/src/assets/customization.svg'; + +import QuickStartsReference from '../_quick-starts-reference.md'; + +# Third-party app integration: Native app + +Use Logto as your identity provider (IdP) to integrate third-party native applications (mobile or desktop) via OpenID Connect (OIDC) or OAuth 2.0 protocol. + +Native apps are mobile or desktop applications that run on user devices. Since they cannot securely store client secrets, they use [PKCE (Proof Key for Code Exchange)](https://auth.wiki/pkce) for secure authorization. Examples include desktop applications like Claude Desktop or VS Code that need to authenticate users to access third-party services. + +## Create a third-party native app in Logto \{#create-a-third-party-native-app-in-logto} + +1. Go to Console > Applications. + +2. Select "Third-party app > Third-party app (Native app)" as the application type. + + - If this is the first time you create an application, click on the **View all** link to see all application types. + + - Otherwise, click on the **Create application** button on the top right corner of the page and select "Third-party app > Third-party app (Native app)" as the application type. + +3. Enter a **name** and **description** for your application and click on the **Create** button. A new third-party native app will be created. + +## Set up the OIDC / OAuth configurations \{#set-up-the-oidc-oauth-configurations} + +To configure Logto as an IdP for your third-party native application: + +1. Provide the **redirect URI** of your third-party application. For native apps, this is typically a custom URL scheme (e.g., `myapp://callback`) or a universal/app link. You can usually find this information in the third-party application's IdP connection settings page. Logto supports multiple redirect URIs—click the **Add another** button to add more. + +2. Retrieve the **client ID** from Logto application details page and enter it into your service provider's IdP connection settings page. + +3. Retrieve the **authorization endpoint** and **token endpoint** from Logto application details page and provide them to your service provider. + + - If your service provider supports OIDC discovery, you can simply copy the **discovery endpoint** from Logto application details page and provide it to your service provider. The service provider will automatically retrieve all OIDC authentication information from the discovery endpoint. + - Otherwise, click on the **Show endpoint details** button to view all the OIDC authentication endpoints. + +4. Ensure the third-party application is configured to use **PKCE** (Proof Key for Code Exchange) during the authorization flow. Most modern OAuth/OIDC libraries support PKCE out of the box. + +--- + + + +## Manage permissions and branding \{#manage-permissions-and-branding} + +Once the OIDC configurations are set up, you can manage what permissions the third-party application can request and customize the branding of the consent screen: + +, + }, + }, + { + type: 'link', + label: 'Consent screen branding', + href: '/integrate-logto/third-party-applications/consent-screen-branding', + description: + 'Personalize the consent screen appearance to match your brand identity and provide a consistent user experience.', + customProps: { + icon: , + }, + }, + ]} +/> + +## Manage your third-party applications \{#manage-your-third-party-applications} + +All third-party applications are listed on the **Applications** page under the **Third-party apps** tab, making it easy to distinguish them from first-party applications. + +## Further readings \{#further-readings} + +Third-party applications diff --git a/docs/quick-starts/third-party/oidc/README.mdx b/docs/quick-starts/third-party/oidc/README.mdx deleted file mode 100644 index a30d8529378..00000000000 --- a/docs/quick-starts/third-party/oidc/README.mdx +++ /dev/null @@ -1,52 +0,0 @@ ---- -slug: /quick-starts/third-party-oidc -sidebar_label: OIDC (Third-party app) -sidebar_custom_props: - description: Use Logto as a third-party OIDC identity provider (IdP) for your application. - logoFilename: 'oidc.svg' ---- - -import QuickStartsReference from './_quick-starts-reference.md'; - -# Integrate third-party app with OIDC / OAuth - -Use Logto as your identity provider (IdP) to integrate third-party apps via OpenID Connect (OIDC) or OAuth 2.0 protocol. - -## Create an third-party OIDC application in Logto \{#create-an-third-party-oidc-application-in-logto} - -Just like how you create a first-party application in Logto, you can also create an application for third-party services that support OIDC. This application will act as an IdP for your third-party applications. - -1. Go to Console > Applications. - -2. Select "Third-party app > OIDC" as the application type. - - - If this is the first time you create an application, click on the **View all** link to see all application types. - - - Otherwise, click on the **Create application** button on the top right corner of the page and select "Third-party app -> OIDC" as the application type. - -3. Just like creating a Logto first-party application, enter a **name** and **description** for your application and click on the **Create** button. A new third-party OIDC application will be created. - -## Setup the OIDC configurations \{#setup-the-oidc-configurations} - -In order to set up Logto as an IdP for your third-party applications, you need to configure the OIDC settings under the application details page. - -1. Provide the **redirect URI** of your third-party application. This is the URL that the third-party application will redirect users to after they are authenticated by Logto. You can usually find this information in the third-party application's IdP connection settings page. Logto supports multiple redirect URIs. You can add more redirect URIs by clicking on the **Add another** button. - -2. Retrieve the **client ID** and **client secret** from Logto application details page and enter them into your service provider's IdP connection settings page. - -3. Retrieve the **authorization endpoint** and **token endpoint** from Logto application details page and provide them to your service provider. - - - If your service provider supports OIDC discovery, you can simply copy the **discovery endpoint** from Logto application details page and provide it to your service provider. The service provider will be able to retrieve all the up to date OIDC authentication information from the discovery endpoint automatically. - - Otherwise, click on the **Show endpoint details** button to view all the OIDC authentication endpoints. - ---- - - - -## Manage your third-party applications \{#manage-your-third-party-applications} - -All third-party applications will be catalogued on the **Applications** page, specifically under the **Third-party apps** tab. This arrangement distinguishes them from first-party applications for you, ensuring easy management. - -## Further readings \{#further-readings} - -Third-party applications diff --git a/docs/quick-starts/third-party/oidc/_quick-starts-reference.md b/docs/quick-starts/third-party/oidc/_quick-starts-reference.md deleted file mode 100644 index c03c7a5205f..00000000000 --- a/docs/quick-starts/third-party/oidc/_quick-starts-reference.md +++ /dev/null @@ -1,11 +0,0 @@ -Under the hood, a third-party app is just a standard OAuth 2.0 / OIDC client. This means you (or the third-party developer) can use any OAuth 2.0 / OIDC library or framework to integrate with Logto. - -If you're not familiar with OAuth 2.0 or OIDC, you can start by following one of our “Traditional web” quick start guides. - -A few things to keep in mind: - -1. Logto currently requires third-party apps to be “Traditional web” apps. In other words, the app needs a backend server (or backend-for-frontend) to securely store the client secret. -2. Most our quick start guides are written for first-party apps, but you can still use them as a reference for third-party app integration. -3. The main difference is that third-party apps will show a consent screen, asking users for explicit permission to access their data. - -You can find more information in our [quick start guides](/quick-starts). diff --git a/docs/quick-starts/third-party/spa/README.mdx b/docs/quick-starts/third-party/spa/README.mdx new file mode 100644 index 00000000000..ab81192538e --- /dev/null +++ b/docs/quick-starts/third-party/spa/README.mdx @@ -0,0 +1,87 @@ +--- +slug: /quick-starts/third-party-spa +sidebar_label: Third-party app (Single page app) +sidebar_custom_props: + description: Integrate a third-party single page application using OIDC / OAuth protocol with PKCE. + logoFilename: 'spa.svg' +--- + +import AuthorizationIcon from '@site/src/assets/authorization.svg'; +import CustomizationIcon from '@site/src/assets/customization.svg'; + +import QuickStartsReference from '../_quick-starts-reference.md'; + +# Third-party app integration: Single page app (SPA) + +Use Logto as your identity provider (IdP) to integrate third-party single page applications (SPAs) via OpenID Connect (OIDC) or OAuth 2.0 protocol. + +Single page apps are client-side web applications that run entirely in the user's browser. Since they cannot securely store client secrets, they use [PKCE (Proof Key for Code Exchange)](https://auth.wiki/pkce) for secure authorization. In this scenario, the client obtains tokens directly from the authorization server without going through a backend. + +A typical example is MCP (Model Context Protocol) integrations, where the MCP Client initiates authentication directly with the auth server to access various MCP Servers—the MCP Server providers don't control the client applications. + +## Create a third-party SPA in Logto \{#create-a-third-party-spa-in-logto} + +1. Go to Console > Applications. + +2. Select "Third-party app > Third-party app (Single page app)" as the application type. + + - If this is the first time you create an application, click on the **View all** link to see all application types. + + - Otherwise, click on the **Create application** button on the top right corner of the page and select "Third-party app > Third-party app (Single page app)" as the application type. + +3. Enter a **name** and **description** for your application and click on the **Create** button. A new third-party SPA will be created. + +## Set up the OIDC / OAuth configurations \{#set-up-the-oidc-oauth-configurations} + +To configure Logto as an IdP for your third-party SPA: + +1. Provide the **redirect URI** of your third-party application. This is the URL that the third-party application will redirect users to after they are authenticated by Logto. You can usually find this information in the third-party application's IdP connection settings page. Logto supports multiple redirect URIs—click the **Add another** button to add more. + +2. Retrieve the **client ID** from Logto application details page and enter it into your service provider's IdP connection settings page. + +3. Retrieve the **authorization endpoint** and **token endpoint** from Logto application details page and provide them to your service provider. + + - If your service provider supports OIDC discovery, you can simply copy the **discovery endpoint** from Logto application details page and provide it to your service provider. The service provider will automatically retrieve all OIDC authentication information from the discovery endpoint. + - Otherwise, click on the **Show endpoint details** button to view all the OIDC authentication endpoints. + +4. Ensure the third-party application is configured to use **PKCE** (Proof Key for Code Exchange) during the authorization flow. Most modern OAuth/OIDC libraries support PKCE out of the box. + +--- + + + +## Manage permissions and branding \{#manage-permissions-and-branding} + +Once the OIDC configurations are set up, you can manage what permissions the third-party application can request and customize the branding of the consent screen: + +, + }, + }, + { + type: 'link', + label: 'Consent screen branding', + href: '/integrate-logto/third-party-applications/consent-screen-branding', + description: + 'Personalize the consent screen appearance to match your brand identity and provide a consistent user experience.', + customProps: { + icon: , + }, + }, + ]} +/> + +## Manage your third-party applications \{#manage-your-third-party-applications} + +All third-party applications are listed on the **Applications** page under the **Third-party apps** tab, making it easy to distinguish them from first-party applications. + +## Further readings \{#further-readings} + +Third-party applications diff --git a/docs/quick-starts/third-party/traditional-web/README.mdx b/docs/quick-starts/third-party/traditional-web/README.mdx new file mode 100644 index 00000000000..d72f4ea089b --- /dev/null +++ b/docs/quick-starts/third-party/traditional-web/README.mdx @@ -0,0 +1,83 @@ +--- +slug: /quick-starts/third-party-traditional-web +sidebar_label: Third-party app (Traditional web) +sidebar_custom_props: + description: Integrate a third-party traditional web application using OIDC / OAuth protocol. + logoFilename: 'traditional-web.svg' +--- + +import AuthorizationIcon from '@site/src/assets/authorization.svg'; +import CustomizationIcon from '@site/src/assets/customization.svg'; + +import QuickStartsReference from '../_quick-starts-reference.md'; + +# Third-party app integration: Traditional web app + +Use Logto as your identity provider (IdP) to integrate third-party traditional web applications via OpenID Connect (OIDC) or OAuth 2.0 protocol. + +Traditional web apps are server-side applications that can securely store client secrets. This is the most common type for third-party integrations, such as enterprise SaaS platforms or partner portals. + +## Create a third-party traditional web app in Logto \{#create-a-third-party-traditional-web-app-in-logto} + +1. Go to Console > Applications. + +2. Select "Third-party app > Third-party app (Traditional web)" as the application type. + + - If this is the first time you create an application, click on the **Third-party app** tab to see all application types. + + - Otherwise, click on the **Create application** button on the top right corner of the page and select "Third-party app > Third-party app (Traditional web)" as the application type. + +3. Enter a **name** and **description** for your application and click on the **Create** button. A new third-party traditional web application will be created. + +## Set up the OIDC / OAuth configurations \{#set-up-the-oidc-oauth-configurations} + +To configure Logto as an IdP for your third-party traditional web application: + +1. Provide the **redirect URI** of your third-party application. This is the URL that the third-party application will redirect users to after they are authenticated by Logto. You can usually find this information in the third-party application's IdP connection settings page. Logto supports multiple redirect URIs—click the **Add another** button to add more. + +2. Retrieve the **client ID** and **client secret** from Logto application details page and enter them into your service provider's IdP connection settings page. Since traditional web apps run on the server side, they can securely store the client secret. + +3. Retrieve the **authorization endpoint** and **token endpoint** from Logto application details page and provide them to your service provider. + + - If your service provider supports OIDC discovery, you can simply copy the **discovery endpoint** from Logto application details page and provide it to your service provider. The service provider will automatically retrieve all OIDC authentication information from the discovery endpoint. + - Otherwise, click on the **Show endpoint details** button to view all the OIDC authentication endpoints. + +--- + + + +## Manage permissions and branding \{#manage-permissions-and-branding} + +Once the OIDC configurations are set up, you can manage what permissions the third-party application can request and customize the branding of the consent screen: + +, + }, + }, + { + type: 'link', + label: 'Consent screen branding', + href: '/integrate-logto/third-party-applications/consent-screen-branding', + description: + 'Personalize the consent screen appearance to match your brand identity and provide a consistent user experience.', + customProps: { + icon: , + }, + }, + ]} +/> + +## Manage your third-party applications \{#manage-your-third-party-applications} + +All third-party applications are listed on the **Applications** page under the **Third-party apps** tab, making it easy to distinguish them from first-party applications. + +## Further readings \{#further-readings} + +Third-party applications diff --git a/docs/use-cases/ai/fragments/_configure-third-party-ai-agent.mdx b/docs/use-cases/ai/fragments/_configure-third-party-ai-agent.mdx index 58b11277b9e..200ccca95f9 100644 --- a/docs/use-cases/ai/fragments/_configure-third-party-ai-agent.mdx +++ b/docs/use-cases/ai/fragments/_configure-third-party-ai-agent.mdx @@ -1,4 +1,4 @@ -import QuickStartsReference from '../../../quick-starts/third-party/oidc/_quick-starts-reference.md'; +import QuickStartsReference from '../../../quick-starts/third-party/_quick-starts-reference.md'; ## Configure third-party AI agent in Logto \{#configure-third-party-ai-agent-in-logto} diff --git a/i18n/de/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx b/i18n/de/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx index e16455d874b..7886a86ebf4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx @@ -32,7 +32,7 @@ Alle erstellten Drittanbieteranwendungen werden auf der Anwendungsseite unter de ## OIDC-Konfigurationen einrichten \{#set-up-the-oidc-configurations} :::note -Bevor du die OIDC-Konfigurationen einrichtest, stelle bitte sicher, dass du [eine OIDC-Drittanbieteranwendung erstellt](/quick-starts/third-party-oidc) hast. +Bevor du die OIDC-Konfigurationen einrichtest, stelle bitte sicher, dass du [eine OIDC-Drittanbieteranwendung erstellt](/quick-starts/third-party-traditional-web) hast. ::: 1. Gib die [**Redirect-URI**](/integrate-logto/application-data-structure#redirect-uris) deiner OIDC-Drittanbieteranwendung an. Dies ist die URL, zu der die Drittanbieteranwendung Benutzer weiterleitet, nachdem sie von Logto authentifiziert wurden. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx b/i18n/de/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx index 63499948739..6c02a61461b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx @@ -1,5 +1,5 @@ --- -slug: /quick-starts/third-party-oidc +slug: /quick-starts/third-party-traditional-web sidebar_label: OIDC (Drittanbieter-App) sidebar_custom_props: description: Verwende Logto als Drittanbieter-OIDC-Identitätsanbieter (IdP) für deine Anwendung. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx index 9f82be492d5..8f51d688f20 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx @@ -32,7 +32,7 @@ Todas las aplicaciones de terceros creadas se catalogarán en la página de Apli ## Configura las configuraciones OIDC \{#set-up-the-oidc-configurations} :::note -Antes de configurar las opciones OIDC, asegúrate de haber [creado una aplicación de terceros OIDC](/quick-starts/third-party-oidc). +Antes de configurar las opciones OIDC, asegúrate de haber [creado una aplicación de terceros OIDC](/quick-starts/third-party-traditional-web). ::: 1. Proporciona el [**redirect URI**](/integrate-logto/application-data-structure#redirect-uris) de tu aplicación de terceros OIDC. Esta es la URL a la que la aplicación de terceros redirigirá a los usuarios después de ser autenticados por Logto. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx index 26255dc66cc..a07aa4989ec 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx @@ -1,5 +1,5 @@ --- -slug: /quick-starts/third-party-oidc +slug: /quick-starts/third-party-traditional-web sidebar_label: OIDC (Aplicación de terceros) sidebar_custom_props: description: Usa Logto como un proveedor de identidad (IdP) OIDC de terceros para tu aplicación. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx b/i18n/fr/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx index e86abe536fb..a85ea9f4827 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx @@ -32,7 +32,7 @@ Toutes les applications tierces créées seront répertoriées sur la page Appli ## Configurer les paramètres OIDC \{#set-up-the-oidc-configurations} :::note -Avant de configurer les paramètres OIDC, veuillez vous assurer d’avoir [créé une application tierce OIDC](/quick-starts/third-party-oidc). +Avant de configurer les paramètres OIDC, veuillez vous assurer d’avoir [créé une application tierce OIDC](/quick-starts/third-party-traditional-web). ::: 1. Fournissez l’[**URI de redirection**](/integrate-logto/application-data-structure#redirect-uris) de votre application tierce OIDC. Il s'agit de l'URL vers laquelle l'application tierce redirigera les utilisateurs après leur authentification par Logto. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx b/i18n/fr/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx index 04e56569527..2a33558d8b8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx @@ -1,5 +1,5 @@ --- -slug: /quick-starts/third-party-oidc +slug: /quick-starts/third-party-traditional-web sidebar_label: OIDC (Application tierce) sidebar_custom_props: description: Utilisez Logto comme fournisseur d'identité OIDC (IdP) tiers pour votre application. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx b/i18n/ja/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx index a20c9e6e952..575a2208ca7 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx +++ b/i18n/ja/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx @@ -32,7 +32,7 @@ Logto は [OpenID Connect (OIDC)](https://auth.wiki/openid-connect) プロトコ ## OIDC 設定を行う \{#set-up-the-oidc-configurations} :::note -OIDC 設定を行う前に、[OIDC サードパーティアプリケーションを作成](/quick-starts/third-party-oidc) していることを確認してください。 +OIDC 設定を行う前に、[OIDC サードパーティアプリケーションを作成](/quick-starts/third-party-traditional-web) していることを確認してください。 ::: 1. OIDC サードパーティアプリケーションの [**リダイレクト URI**](/integrate-logto/application-data-structure#redirect-uris) を入力します。これは、Logto で認証 (Authentication) された後にサードパーティアプリケーションがユーザーをリダイレクトする URL です。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx b/i18n/ja/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx index 34eafc82063..35dee702fe0 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx +++ b/i18n/ja/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx @@ -1,5 +1,5 @@ --- -slug: /quick-starts/third-party-oidc +slug: /quick-starts/third-party-traditional-web sidebar_label: OIDC（サードパーティアプリ） sidebar_custom_props: description: アプリケーションのために Logto をサードパーティ OIDC アイデンティティプロバイダー (IdP) として利用する。 diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx b/i18n/ko/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx index 6e494f2d245..a1e5875f7cc 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx +++ b/i18n/ko/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx @@ -32,7 +32,7 @@ Logto는 [OpenID Connect (OIDC)](https://auth.wiki/openid-connect) 프로토콜 ## OIDC 구성 설정하기 \{#set-up-the-oidc-configurations} :::note -OIDC 구성을 설정하기 전에, [OIDC 타사 애플리케이션을 생성](/quick-starts/third-party-oidc)했는지 확인하세요. +OIDC 구성을 설정하기 전에, [OIDC 타사 애플리케이션을 생성](/quick-starts/third-party-traditional-web)했는지 확인하세요. ::: 1. OIDC 타사 애플리케이션의 [**리디렉션 URI**](/integrate-logto/application-data-structure#redirect-uris)를 입력하세요. 이 URL은 Logto에서 인증 (Authentication) 후 사용자를 타사 애플리케이션으로 리디렉션하는 주소입니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx b/i18n/ko/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx index b04add23263..13beb9a79f4 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx +++ b/i18n/ko/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx @@ -1,5 +1,5 @@ --- -slug: /quick-starts/third-party-oidc +slug: /quick-starts/third-party-traditional-web sidebar_label: OIDC (서드파티 앱) sidebar_custom_props: description: Logto를 서드파티 OIDC 아이덴티티 제공자 (IdP)로 사용하여 애플리케이션을 연동하세요. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx b/i18n/pt-BR/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx index 257d3ea9c20..2278c2cb2bb 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx @@ -32,7 +32,7 @@ Todos os aplicativos de terceiros criados serão catalogados na página de Aplic ## Configurar as configurações OIDC \{#set-up-the-oidc-configurations} :::note -Antes de configurar as configurações OIDC, certifique-se de que você já [criou um aplicativo de terceiros OIDC](/quick-starts/third-party-oidc). +Antes de configurar as configurações OIDC, certifique-se de que você já [criou um aplicativo de terceiros OIDC](/quick-starts/third-party-traditional-web). ::: 1. Forneça o [**redirect URI**](/integrate-logto/application-data-structure#redirect-uris) do seu aplicativo de terceiros OIDC. Esta é a URL para a qual o aplicativo de terceiros irá redirecionar os usuários após serem autenticados pelo Logto. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx b/i18n/pt-BR/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx index c52bfb46a1e..15e30edefe1 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx @@ -1,5 +1,5 @@ --- -slug: /quick-starts/third-party-oidc +slug: /quick-starts/third-party-traditional-web sidebar_label: OIDC (Aplicativo de terceiros) sidebar_custom_props: description: Use o Logto como um provedor de identidade OIDC (IdP) de terceiros para seu aplicativo. diff --git a/i18n/th/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx b/i18n/th/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx index c87849c7e7a..bddfb183f76 100644 --- a/i18n/th/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx +++ b/i18n/th/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx @@ -32,7 +32,7 @@ Logto เป็นบริการข้อมูลระบุตัวต ## ตั้งค่าการกำหนดค่า OIDC \{#set-up-the-oidc-configurations} :::note -ก่อนตั้งค่าการกำหนดค่า OIDC โปรดตรวจสอบว่าคุณได้ [สร้างแอป OIDC บุคคลที่สาม](/quick-starts/third-party-oidc) แล้ว +ก่อนตั้งค่าการกำหนดค่า OIDC โปรดตรวจสอบว่าคุณได้ [สร้างแอป OIDC บุคคลที่สาม](/quick-starts/third-party-traditional-web) แล้ว ::: 1. ระบุ [**redirect URI**](/integrate-logto/application-data-structure#redirect-uris) ของแอป OIDC บุคคลที่สามของคุณ นี่คือ URL ที่แอปพลิเคชันบุคคลที่สามจะเปลี่ยนเส้นทางผู้ใช้กลับมาหลังจากได้รับการยืนยันตัวตนโดย Logto diff --git a/i18n/th/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx b/i18n/th/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx index f3b37b8339e..a34a4d25d76 100644 --- a/i18n/th/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx +++ b/i18n/th/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx @@ -1,5 +1,5 @@ --- -slug: /quick-starts/third-party-oidc +slug: /quick-starts/third-party-traditional-web sidebar_label: OIDC (แอปของบุคคลที่สาม) sidebar_custom_props: description: ใช้ Logto เป็นผู้ให้บริการข้อมูลระบุตัวตน (IdP) แบบ OIDC สำหรับแอปพลิเคชันของคุณ diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx b/i18n/zh-CN/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx index 14995b2ee16..9868b93f5f8 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx @@ -32,7 +32,7 @@ Logto 是基于 [OpenID Connect (OIDC)](https://auth.wiki/openid-connect) 协议 ## 设置 OIDC 配置 \{#set-up-the-oidc-configurations} :::note -在设置 OIDC 配置之前，请确保你已经[创建了 OIDC 第三方应用](/quick-starts/third-party-oidc)。 +在设置 OIDC 配置之前，请确保你已经[创建了 OIDC 第三方应用](/quick-starts/third-party-traditional-web)。 ::: 1. 提供你的 OIDC 第三方应用的 [**重定向 URI**](/integrate-logto/application-data-structure#redirect-uris)。这是第三方应用在用户通过 Logto 认证 (Authentication) 后重定向用户的 URL。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx b/i18n/zh-CN/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx index 67f21a7e105..570ead388d0 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx @@ -1,5 +1,5 @@ --- -slug: /quick-starts/third-party-oidc +slug: /quick-starts/third-party-traditional-web sidebar_label: OIDC（第三方应用） sidebar_custom_props: description: 将 Logto 作为你的应用的第三方 OIDC 身份提供商 (IdP)。 diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx b/i18n/zh-TW/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx index 65622c6d1dc..84549463a8b 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/integrate-logto/third-party-applications/README.mdx @@ -32,7 +32,7 @@ Logto 是一個基於 [OpenID Connect (OIDC)](https://auth.wiki/openid-connect) ## 設定 OIDC 組態 \{#set-up-the-oidc-configurations} :::note -在設定 OIDC 組態前，請確保你已[建立 OIDC 第三方應用程式](/quick-starts/third-party-oidc)。 +在設定 OIDC 組態前，請確保你已[建立 OIDC 第三方應用程式](/quick-starts/third-party-traditional-web)。 ::: 1. 提供 OIDC 第三方應用程式的 [**redirect URI**](/integrate-logto/application-data-structure#redirect-uris)。這是第三方應用程式在使用者經 Logto 驗證後將其導向的 URL。 diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx b/i18n/zh-TW/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx index 5649745b15f..96b77ba0d7e 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/quick-starts/third-party/oidc/README.mdx @@ -1,5 +1,5 @@ --- -slug: /quick-starts/third-party-oidc +slug: /quick-starts/third-party-traditional-web sidebar_label: OIDC（第三方應用程式） sidebar_custom_props: description: 將 Logto 作為你的應用程式的第三方 OIDC 身分提供者 (IdP)。 diff --git a/static-localized/en/img/logo/native.svg b/static-localized/en/img/logo/native.svg new file mode 100644 index 00000000000..2336622fc6f --- /dev/null +++ b/static-localized/en/img/logo/native.svg @@ -0,0 +1,15 @@ + + + + + + + + + + + + + + + diff --git a/static-localized/en/img/logo/spa.svg b/static-localized/en/img/logo/spa.svg new file mode 100644 index 00000000000..b3a6c1d1102 --- /dev/null +++ b/static-localized/en/img/logo/spa.svg @@ -0,0 +1,25 @@ + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/static/_redirects-docs b/static/_redirects-docs index 418c30f90af..dc0655731fc 100644 --- a/static/_redirects-docs +++ b/static/_redirects-docs @@ -268,10 +268,12 @@ /docs/tutorials/get-started/passwordless-sign-in-by-adding-connectors/ /connectors 301 /docs/tutorials/get-started/sign-in-experience /concepts/sign-in-experience 301 /docs/tutorials/get-started/sign-in-experience/ /concepts/sign-in-experience 301 -/integrations/third-party-oidc /quick-starts/third-party-oidc 301 -/integrations/third-party-oidc/ /quick-starts/third-party-oidc 301 +/integrations/third-party-oidc /quick-starts/third-party-traditional-web 301 +/integrations/third-party-oidc/ /quick-starts/third-party-traditional-web 301 /quick-start/java-spring-boot /quick-starts/java-spring-boot 301 /quick-start/java-spring-boot/ /quick-starts/java-spring-boot 301 +/quick-starts/third-party-oidc /quick-starts/third-party-traditional-web 301 +/quick-starts/third-party-oidc/ /quick-starts/third-party-traditional-web 301 /*/quick-start/java-spring-boot /:splat/quick-starts/java-spring-boot 301 /*/docs/tutorials/get-started /:splat/introduction 301 /*/docs/tutorials/get-started/ /:splat/introduction 301