start
Starts the authentication journey with the specified options.
Return
A Node representing the result of the journey start.
Parameters
The name of the journey to start.
A lambda function to configure additional options for the journey.
Starts the authentication journey from a backchannel (transactional) URI received via push notification, QR code, or deep link.
The URI's authIndexType and authIndexValue query parameters are extracted and forwarded to the AM authenticate endpoint. The URI's host is validated against JourneyConfig.serverUrl to ensure the backchannel URI originated from the configured server. All other URI components (path, realm) are ignored; the authenticate endpoint is always reconstructed from JourneyConfig.serverUrl and JourneyConfig.realm.
Host validation only establishes that the URI names the configured server. It does not establish that the transaction belongs to the current user, so confirm the transaction details with the user before completing the journey.
authIndexType is forwarded as supplied by the URI rather than restricted to transaction, so this method also works if AM ever routes another authIndexType through a backchannel redirectUri. See the AM Backchannel Authentication design (SDKS-4734) for the iOS implementation this mirrors.
Return
A Node representing the result. Returns FailureNode immediately (without a network call) if the Journey is not configured with a JourneyConfig carrying a usable, absolute HTTP(S) JourneyConfig.serverUrl, if the URI is opaque (non-hierarchical), if the URI host does not match JourneyConfig.serverUrl, or if either required query parameter is absent or blank.
Parameters
The URI supplied by the backchannel initiation (e.g. from a push notification payload or QR code). Must be a hierarchical URI whose authIndexType and authIndexValue query parameters are present and non-blank.
A lambda to configure additional options (e.g. Option.forceAuth, Option.noSession) for this request.