Dispose the native Journey instance and release runtime state.
Promise resolved when disposal completes.
Returns the native Journey instance identifier.
Native Journey instance identifier.
Explicitly initialize the native Journey instance.
Native Journey instance identifier.
Logout active Journey user/session.
true when logout succeeds.
Advance an active Journey by applying callback input.
Optionalinput: JourneyNextInputCallback value payload for the active node.
Next Journey node.
Refresh active Journey user access token.
Refreshed session payload, or null when no active session exists.
Resume a suspended Journey flow from a deep link URL.
Resume URI provided by native/server.
Resumed Journey node.
Revoke active Journey user access/refresh tokens.
true when revoke completes.
Resolve active Journey SSO token payload.
SSO token payload, or null when no active session exists.
Start a Journey by name.
Journey/tree name configured on the server.
Optionaloptions: JourneyStartOptionsOptional start flags.
The first Journey node.
Start a Journey from an AM/AIC backchannel (transactional) redirect URI.
The gateway federation service initializes the transaction via AM's
/authenticate/backchannel/initialize endpoint and delivers the returned
redirectUri to the app through its own channel (push notification, QR
code, deep link). This method extracts the authIndexType and
authIndexValue query parameters from the URI and drives the standard
Journey authenticate flow — the URI itself is never opened as a browser
URL, and the authenticate endpoint is always reconstructed from the
Journey config (serverUrl + realm).
Gateway-provided redirectUri value.
Optionaloptions: JourneyBackchannelOptionsOptional backchannel flags. Both default to false,
matching native behavior.
The first Journey node, using the same node contract as
start/resume. URI validation failures (missing config, malformed URI,
missing or whitespace-only authIndexType/authIndexValue, URI host not
matching the configured serverUrl) resolve as FailureNode payloads
without a network call; expired/not-found/completed transactions surface
AM's message on an ErrorNode.
// Gateway payload: { transaction, redirectUri }
const node = await client.startBackchannel(payload.redirectUri);
if (node.type === 'ContinueNode') {
// render step-up callbacks, then: client.next(...)
}
Mirrors the native start(backchannelUri:) capability (SDKS-5156 iOS /
SDKS-5157 Android). authIndexType is parsed from the URI rather than
hardcoded to transaction. URI validation runs natively before any
network call on both platforms with identical outcomes. Host validation
only establishes that the URI names the configured server; it does not
establish that the transaction belongs to the current user — confirm
transaction details with the user before completing the flow.
Resolve active user session details.
Session payload, or null when no active session exists.
Resolve active Journey userinfo claims.
Userinfo payload, or null when no active session exists.
Native-backed Journey client contract.