How it Works: Sign In with Didit
Didit's Sign In solution offers a secure and user-friendly way for users to authenticate with your application using their Didit account. This process utilizes QR codes for desktop users and direct links for mobile users, ensuring a smooth experience across all devices.
Initiate Sign In
- Your application redirects the user to Didit's authorization endpoint
- Parameters include:
client_id
: Your application's unique identifierscope
: Requested user information (e.g., "openid profile email")redirect_uri
: Where to send the user after authentication
Check out our API Reference for detailed instructions on initiating the sign-in process.
Generate Authentication Request
- Didit's system creates a unique session for the authentication request
- For desktop: A QR code is displayed in your application
- For mobile: A clickable link is presented in your application
User Interaction
- Desktop: User scans the QR code with their mobile device
- Mobile: User clicks the provided link
- Both actions open the Didit mobile app
Authentication in Didit App
- User is presented with the sign-in request in the Didit app
- They can review the requested information and approve the sign-in
Authentication and Data Sharing
- Upon approval, the user is authenticated
- Requested user information is securely prepared for transfer
Completion
- User is redirected back to your application with an authorization code
- Your application exchanges this code for access and ID tokens
- You can now use these tokens to access user information and authenticate the user in your system
Key Features
-
Cross-Platform Compatibility
- Seamless experience on both desktop and mobile devices
- QR code for desktop users
- Direct link for mobile users
-
Customizable Information Requests
- Flexibility to request specific user information (scopes)
- Common scopes include: profile, email, phone, etc.
For a list of supported scopes, refer to our User Scopes page.
-
User-Controlled Information Sharing
- Users have full control over which information to share
- Transparent process enhances trust and compliance
-
Secure Authentication
- Utilizes OpenID Connect (OIDC) protocol for robust security
- No need to handle passwords or sensitive data directly
-
Single Sign-On (SSO)
- Users can access multiple applications with a single Didit account
- Improves user experience and reduces password fatigue
-
Easy Integration
- Simple API calls to initiate the process
- SDK available for streamlined implementation
We recommend using our SDK for a more seamless integration experience.
- Token-Based Authentication
- Secure access and ID tokens for ongoing authentication
- Refresh tokens available for extended sessions without re-authentication