Skip to main content
Integrate Connect alongside your existing login. Your team connects the client SDK to your backend, authorizes enrollment and management and verifies passkey login results before creating a session.

1. Explore the Demo

Use the demo application to try enrollment after login, returning passkey login and passkey management. It uses Amazon Cognito; the Cognito guide explains that integration. The demo is optional. If you already know your intended experience, start with your user journey decisions.

2. Technical Details

1

Agree on the journeys and responsibilities

Identify your login surfaces, account identifiers, fallback and recovery paths. Choose when to offer enrollment and which login patterns to use. Your product and identity teams should agree on these decisions before engineering starts.Use integration planning for the handoff and login approaches to compare identifier-first and passkey-button experiences.
2

Configure the relying party and project

Choose the RP ID and configure your web origins or native app associations. Review RP ID configuration before creating credentials you intend to keep.Set up development and production projects as appropriate for your deployment. Confirm the selected project when copying configuration from the Management Console.
3

Implement backend support

Your backend authorizes Connect tokens for the authenticated account and verifies signed passkey results before creating your existing session. Keep API credentials on the server and grant only the permissions needed by each service.Follow backend setup and Backend API authentication. Connect does not replace your account eligibility, recovery or session policies.
4

Integrate your clients

For web, install the Web SDK, then integrate login, enrollment and management with the web guide.For native apps, install the iOS SDK or Android SDK, then follow the native integration guide. Your app renders the screens and handles the SDK’s returned states.Run the enrollment eligibility check after each authenticated login, including fallback. A user who has a passkey elsewhere may still need one on this device.
5

Verify and roll out

Complete the verification checklist with your supported devices and fallback methods. Start with internal testers, then expand using gradual rollout.Review both passkey creation and actual login usage. Investigate cancellations, fallback and backend session failures before increasing exposure.

3. Get the Source Code from GitHub

The SDK pages link to source repositories and example applications. For access to the Cognito demo application’s source or assistance adapting a flow to your identity system, contact your Corbado representative. See integration support for working with Corbado’s engineers.