Verifiable links

Edit online

Verifiable link files are essential components of app-to-app linking and deep linking strategies on Android and iOS platforms. They facilitate a cohesive user experience by enabling smooth navigation between mobile apps and associated websites or other apps. They enhance the integration and interoperability of the digital ecosystem on mobile devices.

These files are assetlinks.json for Android and apple-app-site-association for iOS. They play a crucial role in enabling seamless navigation and communication between different digital experiences on mobile devices.

They serve as verification mechanisms to ensure that the app is authorized to handle specific URLs or links. They enhance the user experience by allowing direct navigation between different app environments without any intermediate steps.

Use cases

The following examples are just a few potential use cases where the Verifiable Link Files are used to enable seamless navigation, app-to-app communication, deep linking, and personalized experiences on mobile platforms.
Deep linking
Deep linking allows users to navigate directly to specific content within a mobile app from an external source, such as a website or another app. The verifiable link files play a crucial role in enabling deep linking functions. They verify the association between the app and the external source, allowing the app to handle deep links and open specific screens or content within the app when triggered.
FIDO and passkey
Verifiable link files are used to establish connections and enable seamless navigation between mobile apps and associated websites or other apps. These files verify the association between apps and external sources, which facilitates deep linking and app-to-app communication.
App-to-app communication
In scenarios where multiple apps need to communicate with each other, the verifiable link files establish associations between the apps. These files enable seamless app-to-app communication. For example, one app might need to pass data, or trigger actions in another app. The linking files ensure that the communication is secure and authorized between the apps.
Universal links (iOS)
Universal links, facilitated by the apple-app-site-association file, provide a seamless transition from a website to an associated iOS app. Use cases for universal links include scenarios where an app provides enhanced functions or a personalized experience compared to the website. When a user taps a universal link on the website, the associated app is opened directly, which enhances the user engagement and interaction.
Android app links (Android)
Android App Links, established through the assetlinks.json file, enable a seamless transition from a website to the associated Android app. It is useful in scenarios where the app offers a richer user experience or extra features compared to the website. Users can navigate directly to the app, and bypass the app chooser dialog, which improves the overall user journey.
Single sign-on (SSO)
Verifiable link files can also be used along with single-sign-on (SSO) systems. When a user signs in to a website or an app, the linking files can verify the association with other apps. Authentication and access are enabled automatically without any more login credentials. It streamlines the user experience and reduces friction in a multi-app ecosystem.
Personalization and user engagement
Verifiable link files can be used to personalize the user experience based on user preferences and app usage. By establishing connections between apps and associated websites, relevant content and information can be seamlessly presented to users across different platforms. It enhances user engagement and encourages app adoption.
Parent topic: Managing applications

Configuring verifiable links

Edit online

To configure verifiable links, you must configure the appropriate default settings for your applications.

Before you begin

  • You must have administrative permission to complete this task.
  • Log in to the IBM® Verify administration console as an Administrator.

Procedure

  1. Upload files
    1. Select Applications > Applications > Application settings.
    2. Select Apple app-site association or Google digital asset links.
    3. Edit the current version of the platform-specific file in the text box.
      Note: The JSON structure of the file must match the format for Android or iOS.
      If the changes are valid, the Save changes button is enabled.
    4. Select Save changes.
  2. Revert changes
    Because changes are applied to all mobile apps immediately, a misconfiguration is disruptive. It must be replaced with a previously working version. A history of the last 5 versions of each file is provided.
    1. Extend a previous entry.
    2. Select the Copy icon.
    3. Paste that previous version into the textbox for the Current version.
    4. Select Save Changes.

Generating verifiable links

Edit online

IBM Verify supports the generation of verifiable links for registration and login.

About this task

To trigger those links to be generated, the custom attributes openAppRegistration or openAppLogin must be added to the relevant registration profile.

For registration profiles that have the custom attributes openAppRegistration or openAppLogin configured on a mobile device, links replace QR codes. The links are based on the settings in the registration profile advanced settings.

Procedure

  1. Select Authentication > Registration profiles.
  2. Select Edit on the relevant profile.
  3. Select Next.
  4. Go to Advanced settings.
    • For registration, add openAppRegistration as the attribute name.
      Its value can be encoded with the following values.
      Default
      The default value generates a link for the IBM Verify mobile apps and points to https://idass.ice.ibmcloud.com/register...
      A custom domain
      For example, https://my-company.com/registration?code=@code@&name=@accountName@&location=@registrationUri@ generates a link for the custom app where the macros get substituted with the relevant values. The parameter names are customizable. The macros (surrounded by @) cannot be changed.
      The following attributes are supported as macros.
      • code
      • accountName
      • registrationURI
      • number
      • platform
    • For login, add openAppLogin as the attribute name.
      Its value can be encoded with the following values.
      Default
      The default value generates a link for the IBM Verify mobile apps and points to https://idass.ice.ibmcloud.com/login...
      A custom domain
      For example, https://my-company.com/login?code=@lis@&name=@serviceName@&location=@location@ generates a link for the custom app where the macros get substituted with the relevant values. The parameter names are customizable. The macros (surrounded by @) cannot be changed.
      The following attributes are supported as macros.
      • lsi
      • serviceName
      • location
      • expiry
  5. Select Save.