Skip to main content

Overview

Check out the SDK Authentication guide on the available SDK authentication schemes, and how to authenticate with the Junction Mobile SDK.

Mobile SDK Authentication

Learn how to authenticate your mobile app user with Junction Mobile SDK.

Accessing Junction API

You can access Junction API through VitalClient with typed request methods and response models.

Typed API access is not yet available in React Native.
You can obtain a URL to the Junction Link Widget through VitalClient.linkWidgetUrl. Note that the URL contains a short-lived token with 10-minute expiry. For the redirectUrl, you should set it to a URL with a custom URL scheme which your app would register to handle.

Core SDK Status

You can inspect the status of the Core SDK for troubleshooting, as well as for your own business logic. For example, you may reconcile your user session and the Junction SDK sign-in based on the Core SDK status. The SDK normally reports one of the following status combinations:

Get the current status

Observe status changes over time

Get Current Junction User ID

Aside from the Core SDK Status, you can also query the Junction User ID of the signed-in user:

Reset the SDK (Sign Out)

Refer to the Sign Out section in the SDK Authentication guide.

Verbose Logging to Console/Logcat

You can enable verbose logging to have a deeper look into how Junction Mobile SDK is reacting to your calls, as well as all the automatic behaviors that the SDK is performing in background. To avoid any missing log entry, you should enable verbose logging as early as possible — preferably before any usage of any Junction Mobile SDKs.
On Android, verbose logging is enabled by default when running as a debuggable build (i.e., with ApplicationInfo.FLAG_DEBUGGABLE).