Skip to main content
The Connect Android SDK handles passkey ceremonies through Android Credential Manager. Your existing backend remains responsible for account eligibility and application sessions.
1

Install

Use Android API level 26 or later and enable mavenCentral() in your dependency repositories.
Dependencies are resolved from published packages. See Maven Central for available versions.
2

Configure the app and backend

Follow native RP ID configuration to associate your app with the relying party through Digital Asset Links.Implement backend support for Connect tokens and signed-passkey verification. Do not put Backend API keys in the app.
3

Initialize

Create one instance with the application context and reuse it. Calls that open a Credential Manager prompt, such as login and passkey creation, take the current Activity as a separate argument. Use your project’s frontend API suffix if it differs.
4

Implement the SDK flows

Follow the native integration guide for enrollment, login, fallback and management. Connect tokens come from your backend; passkey login results return to it for verification before a session is issued.

​
Enrollment and lifecycle

Keep the SDK and its Credential Manager dependency up to date as Android and credential providers evolve. Test login and passkey management after leaving the screen open, as well as background/foreground transitions. Use isAppendAllowed(connectTokenProvider = ..., situation = ...) for enrollment in a configured authenticated context. The SDK also supports accepted-credential signaling during management when enabled by the backend and supported by the provider. See enrollment contexts for API details and the current conditional-create limitation, and native Signal API for provider behavior.

​
Verify

Test on a supported device with a configured credential provider. Check RP ID association, enrollment, successful login, cancellation, fallback and passkey deletion. See Android testing. The SDK source and example app show native API usage.