From 1cd5016825417c7ada2df101624e46b6c36bb308 Mon Sep 17 00:00:00 2001 From: wangsijie Date: Tue, 21 Jan 2025 11:55:18 +0800 Subject: [PATCH] fix: correct the method of linking social identities --- docs/end-user-flows/account-settings/by-account-api.mdx | 4 ++-- .../end-user-flows/account-settings/by-account-api.mdx | 4 ++-- .../end-user-flows/account-settings/by-account-api.mdx | 4 ++-- .../end-user-flows/account-settings/by-account-api.mdx | 4 ++-- .../end-user-flows/account-settings/by-account-api.mdx | 4 ++-- .../end-user-flows/account-settings/by-account-api.mdx | 4 ++-- 6 files changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/end-user-flows/account-settings/by-account-api.mdx b/docs/end-user-flows/account-settings/by-account-api.mdx index 2df019c5ac9..ce9968eb57b 100644 --- a/docs/end-user-flows/account-settings/by-account-api.mdx +++ b/docs/end-user-flows/account-settings/by-account-api.mdx @@ -265,10 +265,10 @@ curl -X POST https://[tenant-id].logto.app/api/verifications/social/verify \ The `connectorData` is the data returned by the social connector after the user authorizes the application, you need to parse and get the query parameters from the `redirectUri` in your callback page, and wrap them as a JSON as the value of the `connectorData` field. -Finally, you can use the `PATCH /api/my-account/identities` endpoint to link the social connection. +Finally, you can use the `POST /api/my-account/identities` endpoint to link the social connection. ```bash -curl -X PATCH https://[tenant-id].logto.app/api/my-account/identities \ +curl -X POST https://[tenant-id].logto.app/api/my-account/identities \ -H 'authorization: Bearer ' \ -H 'logto-verification-id: ' \ -H 'content-type: application/json' \ diff --git a/i18n/es/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx index d55d1381e97..2d38e2fd1f5 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx @@ -265,10 +265,10 @@ curl -X POST https://[tenant-id].logto.app/api/verifications/social/verify \ El `connectorData` es el dato devuelto por el conector social después de que el usuario autorice la aplicación, necesitas analizar y obtener los parámetros de consulta del `redirectUri` en tu página de callback, y envolverlos como un JSON como el valor del campo `connectorData`. -Finalmente, puedes usar el endpoint `PATCH /api/my-account/identities` para vincular la conexión social. +Finalmente, puedes usar el endpoint `POST /api/my-account/identities` para vincular la conexión social. ```bash -curl -X PATCH https://[tenant-id].logto.app/api/my-account/identities \ +curl -X POST https://[tenant-id].logto.app/api/my-account/identities \ -H 'authorization: Bearer ' \ -H 'logto-verification-id: ' \ -H 'content-type: application/json' \ diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx b/i18n/fr/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx index 0a9b30f6d5e..03e1acb6b77 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx @@ -265,10 +265,10 @@ curl -X POST https://[tenant-id].logto.app/api/verifications/social/verify \ Le `connectorData` est les données retournées par le connecteur social après que l'utilisateur a autorisé l'application, vous devez analyser et obtenir les paramètres de requête de l'`redirectUri` dans votre page de rappel, et les envelopper en JSON comme valeur du champ `connectorData`. -Enfin, vous pouvez utiliser le point de terminaison `PATCH /api/my-account/identities` pour lier la connexion sociale. +Enfin, vous pouvez utiliser le point de terminaison `POST /api/my-account/identities` pour lier la connexion sociale. ```bash -curl -X PATCH https://[tenant-id].logto.app/api/my-account/identities \ +curl -X POST https://[tenant-id].logto.app/api/my-account/identities \ -H 'authorization: Bearer ' \ -H 'logto-verification-id: ' \ -H 'content-type: application/json' \ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx b/i18n/ja/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx index d832c03c112..693027a6676 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx +++ b/i18n/ja/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx @@ -265,10 +265,10 @@ curl -X POST https://[tenant-id].logto.app/api/verifications/social/verify \ `connectorData` は、ユーザーがアプリケーションを認可 (Authorization) した後にソーシャルコネクターから返されるデータで、コールバックページの `redirectUri` からクエリパラメータを解析して取得し、それを JSON として `connectorData` フィールドの値としてラップする必要があります。 -最後に、`PATCH /api/my-account/identities` エンドポイントを使用してソーシャル接続をリンクできます。 +最後に、`POST /api/my-account/identities` エンドポイントを使用してソーシャル接続をリンクできます。 ```bash -curl -X PATCH https://[tenant-id].logto.app/api/my-account/identities \ +curl -X POST https://[tenant-id].logto.app/api/my-account/identities \ -H 'authorization: Bearer ' \ -H 'logto-verification-id: ' \ -H 'content-type: application/json' \ diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx b/i18n/pt-BR/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx index 2ca57d3b02d..3cf81882355 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx @@ -265,10 +265,10 @@ curl -X POST https://[tenant-id].logto.app/api/verifications/social/verify \ O `connectorData` são os dados retornados pelo conector social após o usuário autorizar o aplicativo, você precisa analisar e obter os parâmetros de consulta do `redirectUri` em sua página de callback e envolvê-los como um JSON como o valor do campo `connectorData`. -Finalmente, você pode usar o endpoint `PATCH /api/my-account/identities` para vincular a conexão social. +Finalmente, você pode usar o endpoint `POST /api/my-account/identities` para vincular a conexão social. ```bash -curl -X PATCH https://[tenant-id].logto.app/api/my-account/identities \ +curl -X POST https://[tenant-id].logto.app/api/my-account/identities \ -H 'authorization: Bearer ' \ -H 'logto-verification-id: ' \ -H 'content-type: application/json' \ diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx b/i18n/zh-CN/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx index 3f6b129fbf5..daee7ef0cf9 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/end-user-flows/account-settings/by-account-api.mdx @@ -265,10 +265,10 @@ curl -X POST https://[tenant-id].logto.app/api/verifications/social/verify \ `connectorData` 是用户授权应用程序后社交连接器返回的数据，你需要在回调页面中解析并获取 `redirectUri` 的查询参数，并将其包装为 JSON 作为 `connectorData` 字段的值。 -最后，你可以使用 `PATCH /api/my-account/identities` 端点链接社交连接。 +最后，你可以使用 `POST /api/my-account/identities` 端点链接社交连接。 ```bash -curl -X PATCH https://[tenant-id].logto.app/api/my-account/identities \ +curl -X POST https://[tenant-id].logto.app/api/my-account/identities \ -H 'authorization: Bearer ' \ -H 'logto-verification-id: ' \ -H 'content-type: application/json' \