DeviceBindingCallback
Journey callback for handling device binding operations in authentication flows.
This callback enables applications to bind a device to a user's identity by creating and registering cryptographic keys with various authentication methods. It supports multiple authentication types including biometric, PIN, and no authentication.
The callback handles the complete device binding lifecycle:
Key pair generation with optional attestation
User authentication based on the specified authentication type
JWT signing with the generated keys
Storage of user key metadata
Error handling and cleanup on failures
See also
Properties
The attestation configuration specifying what type of key attestation should be included when generating the key pair. Can be None for no attestation or contain a challenge for hardware attestation.
Error message to be sent to the server if the device binding operation fails. Can be overridden to provide custom error messages.
The description to display in authentication prompts. Explains why authentication is required and what will happen.
The type of authentication required to access the cryptographic keys. Determines whether biometric, PIN, or no authentication is required.