Skip to main content
Version: v0

3. Set Registration Redirect URI

Last updated on

This URI lets us know where to redirect new users when they register using an email. Whenever a new user registers using Beyond Identity, we send out an email to verify their identity. By default, the link in that email redirects a user to our Native Platform Authenticator. In order to redirect to your own iOS/Android application, you will need to specify this URI to be either an app scheme or a universal url / app link.

iOS Setup Instructions​

Apple supports two ways of deep linking into an app. Pick one of the following and follow the guide:

Android Setup Instructions​

Android supports two way of deep linking into an app. Pick one of the following and follow the guide:

A note on AppSchemes

While app schemes are trivial to set up and great for testing, we recommend using universal URLs in a production setting. The same app scheme can be registered by multiple apps, allowing other apps to pretend to be your app.

Supporting Multiple OSs​

In order to support registration on both iOS and Android, there are a couple of ways to do it depending on which method you chose to deep link into your app above.

  1. Set up Universal URLs for your iOS app
  2. Set up App Links for your Android app
  3. Make sure you use the the exact same URL for both iOS and Android

Method 2: Custom URL on your domain​

  1. Set up a custom path on your domain/backend (e.g https://example.com/registration-redirect)
  2. Detect the OS in the browser and use that to launch the appropriate app by app scheme/universal url/app link

Updating Registration Redirect URI​

See Account Configuration in order to update the registration redirect URI once you've gone through the above steps.

Debugging​

Universal URLs / App Links can take a bit of time to set up. In order to save time and get up and running more quickly, we recommend using app schemes during development.

URL Selection​

When it comes to selecting a registration redirect URI to use, we're not picky. you can use anything you want as long as it's a valid URL. Examples of valid app schemes / URLs to use include:

https://example.com/
https://example.com/anypathyouwant
acme-app://
acme-app://anypathyouwant

While we don't enforce a specific path to be specified as part of a URL, you might find that it's useful in order to distinguish between multiple URLs being deep-linked into your app.