From ce8313f876d64abfc1a9b173b2a189e4bf9fc705 Mon Sep 17 00:00:00 2001 From: himeshsiriwardana Date: Tue, 30 Jul 2024 09:17:01 +0530 Subject: [PATCH] minor fixes --- .../add-passwordless-login-with-passkey.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/en/includes/guides/authentication/passwordless-login/add-passwordless-login-with-passkey.md b/en/includes/guides/authentication/passwordless-login/add-passwordless-login-with-passkey.md index 4195aacfe0..2f671bcbc1 100644 --- a/en/includes/guides/authentication/passwordless-login/add-passwordless-login-with-passkey.md +++ b/en/includes/guides/authentication/passwordless-login/add-passwordless-login-with-passkey.md @@ -155,7 +155,7 @@ Follow the steps below to use an enrolled passkey to sign in to an application. ## Make application a FIDO trusted app -If you are working with a mobile application that implements passkeys, making it a FIDO trusted app allows the hosting platform (iOS or Android) to validate the authenticity of the application by calling the corresponding validation service. This ensures that the authentication requests originate from a legitimate application, safeguarding against malicious attempts to steal credentials. +If you wish to integrate passkeys for a mobile application using [app-native authentication]({{base_path}}/guides/authentication/app-native-authentication/), it is required to make the application a FIDO trusted app. By doing so, you allow the hosting platform (iOS or Android) to validate the authenticity of the application. This ensures that the authentication requests originate from a legitimate application, safeguarding against malicious attempts to steal credentials. !!! note @@ -163,13 +163,13 @@ If you are working with a mobile application that implements passkeys, making it {% if product_name == "WSO2 Identity Server" %} -It is required by the validation services of [iOS](https://developer.apple.com/documentation/xcode/supporting-associated-domains){target="_blank"} and [Android](https://developer.android.com/identity/sign-in/credential-manager#add-support-dal){target="blank"} to have details about the application exposed in a public URL. By following this guide, you are publishing details about your app to one of the following endpoints of {{product_name}} based on the platform. +By following this guide, you enable {{product_name}} to host details about your applications in the following endpoints as required by the validation services of [Android](https://developer.android.com/identity/sign-in/credential-manager#add-support-dal){target="blank"} and [iOS](https://developer.apple.com/documentation/xcode/supporting-associated-domains){target="_blank"}. - For Android - `{{base_url}}/.well-known/assetlinks.json` - For iOS - `{{base_url}}/.well-known/apple-app-site-association` -Therefore, ensure public requests to `/assetlinks.json` and `/apple-app-site-association` on your domain are mapped to the corresponding local endpoints of {{product_name}}. +Make sure `/assetlinks.json` and `/apple-app-site-association` endpoints of your domain, are mapped to the corresponding local endpoints of {{product_name}}. !!! note "Third-party data exposure" @@ -183,7 +183,7 @@ Therefore, ensure public requests to `/assetlinks.json` and `/apple-app-site-ass ``` Once configured, a confirmation popup will appear when enabling the feature and this consent will be recorded and published as an audit log. -To publish app details to the relevant endpoint, +To publish app details to the endpoints, 1. On the {{product_name}} Console, go to **Applications** and select your application. @@ -217,7 +217,7 @@ It is required by the validation services of [iOS](https://developer.apple.com/d !!! note - The URLs to which Asgardeo publishes app details are common to all organizations. This means your app details will reside together with the app details of other organizations. While this is not a security concern, it is important to note that other organization users may learn details about your applications through these URLs. + Asgardeo publishes app details to URLs which are common to all organizations. This means your app details will reside together with the app details of other organizations. While this is not a security concern, it is important to note that other organization users may learn details about your applications through these URLs. If this is not desirable for your use case, you may use [custom domains]({{base_path}}/guides/branding/configure-custom-domains/) for your organization and publish app details to [custom endpoints](#for-custom-domains).