Package-level declarations

Types

Link copied to clipboard

The activation step fragment, it has 2 ways for activation, discovery service and QR code scanning

Link copied to clipboard

The basic authentication step fragment

Link copied to clipboard

Cert authentication step fragment

Link copied to clipboard

The crash report consent step fragment

Link copied to clipboard

Discovery activation step.

Link copied to clipboard

Enable Biometric step fragment

Link copied to clipboard

The end user license agreement step

Link copied to clipboard

Represents the only step of the logout flow.

Link copied to clipboard

Represents the flow step to activate with MDM.

Link copied to clipboard

The OAuth authentication step fragment

Link copied to clipboard

Represents the final step of authentication flow, where it retrieves user detail information and client policies.

Link copied to clipboard

Step to Check current user if match with server user

Link copied to clipboard

After VerifyPasscodeFragment step, flow might need to call API to retrieve the offline encryption key for multiple user model offline apps. In that case if the offline key cannot be retrieved, the current onboarding user should be marked 'onboarded = false', so he/she must re-launch the onboarding process with either 'onboarding', 'create_account' or 'forget_passcode' flows. This step is to give flow a chance to terminate the current flow.

Link copied to clipboard
Link copied to clipboard

Represents the QR reader fragment step to activate the application.

Link copied to clipboard

Represents the flow step fragment of the reset flow.

Link copied to clipboard

The saml authentication step fragment

Link copied to clipboard

Set pass code step fragment

Link copied to clipboard
Link copied to clipboard

Unlock application with biometric step fragment

Link copied to clipboard

The usage consent step fragment

Link copied to clipboard

The step to verify passcode