Recognized Browser Flow

🎯 Purpose

Streamlined authentication flow for browsers that have been previously trusted through the "Remember Me" functionality. This flow reduces authentication friction while maintaining security through multi-factor verification.

---

🔄 Detailed Process Flow

🚀 Step 1: Initial Authentication Request

• User Action: User clicks "Sign In" button on RP's login page
• Redirect Process: User redirected via OIDC redirect URL to REL-ID Web Authentication
• Browser Recognition: System identifies browser as previously trusted
• Session Context: Remembered browser information retrieved

👥 Step 2: Account Chooser Screen

• Screen Presentation: Account Chooser displayed instead of username entry
• User Display: Shows previously authenticated user accounts for this browser
• Visual Elements: User profiles displayed with usernames and any associated information
• User Selection: User selects their account from the available options

🎯 Step 3: Sign-In Options Presentation

• Immediate Options: Available authentication methods displayed directly
• User Context: Options based on selected user's profile and registered factors
• Administrator Control: Available factors limited by system configuration
• Streamlined UX: No need for first factor authentication in most cases

🔒 Step 4: Default Method Selection

• Automatic Selection: First available Sign-In option chosen by default
• User Prompt: User asked to complete authentication with selected method
• Method Types: Push notification, TOTP, SMS OTP, Email OTP based on availability

🔄 Step 5: Alternative Method Selection (Optional)

• Choice Available: User can opt out of default selected option if multiple methods available
• Method Selection: User chooses preferred authentication method
• User Control: Provides flexibility in authentication approach

🔐 Step 6: Authentication Completion

• Method Execution: User completes chosen authentication method
• Validation: System verifies authentication credentials
• Single Factor: Often only second factor required due to browser trust

🎉 Step 7: Successful Authentication

• Session Establishment: Authenticated session created
• Redirect Process: User redirected back to RP's callback URL
• Authorization Code: Callback includes authorization code for token exchange
• Streamlined Experience: Faster authentication compared to unrecognized browser

---

📊 Recognized Browser Flow Diagram

---