Co-Auth: Documentation
WebsiteDocumentaionGithub
  • 🏠Welcome to Co-Auth Documentation
  • Getting Started
    • Co-Auth Modules & Release Status
      • Time Based OTP
      • Reconfirm
    • Architecture
      • Components Flow
      • Integration Overview
        • Integration with Co-Auth
      • Tech Stack
    • Requirements & Prerequisites
    • Installation
      • Setup as a Test / Dev environment
        • Test Setup on Red Hat OpenShift
        • Test Setup on Kubernetes
        • Cloud Provider
        • Development Setup
      • Setup on Production
  • using COAUTH
    • 🕐Key Concepts
  • API
    • 🕐Overview
    • 🕐API Documentation
  • Advanced Topics
    • Customization
      • Database
      • 🕐Caching
      • Good to Have
  • contribute to CoAuth
    • Contribute
    • Setup a Build Environment
  • Usecases
    • 🙂Articles
    • Implementation Use Case
      • 🕐2nd Factor for Authentication
      • 🕐Securing Internal Pages
      • 🕐Transaction verification
      • 🕐Safeguard from MTM, Keystroke attacks
      • 🕐QR are not just for Login
  • administration
    • 🕐Coming Soon
  • Group 1
    • Behind the Scenes
      • Sponsors
      • Adopters
      • Core Contributors
Powered by GitBook
On this page

Was this helpful?

  1. Getting Started
  2. Co-Auth Modules & Release Status

Reconfirm

Module Reconfirm, with its dual verification modes, offers a versatile solution for user authentication, allowing applications to strike a balance between maintaining confidentiality and providing a user-friendly experience. The two modes cater to different security needs, demonstrating adaptability in the verification process.

Mode 1: Conventional Display and Confirm

  1. Information Display:

    • Non-sensitive text is displayed on the screen for user review.

    • This can include any information to be re-typed.

  2. User Confirmation:

    • Users are prompted to re-enter the displayed information for verification.

    • Follows a similar model to GitHub's delete actions and many other websites.

  3. Validation:

    • The system compares the re-entered information with the displayed data.

    • If there is a match, the verification is successful.

Mode 2: Discreet Pass and Confirm with Hint

  1. Information Passing:

    • Sensitive information, such as date of birth or city of birth, is passed by the application during Co-Auth verification generate request.

    • This information is not displayed on the screen to maintain confidentiality.

  2. Hint Presentation:

    • Users receive a hint or prompt guiding them to accurately re-enter the sensitive data.

    • The hint provides contextual information without revealing the actual details.

  3. User Input:

    • Users input the information based on the provided hint.

  4. Validation:

    • The system validates the user-input data against the initially passed sensitive information.

    • Security measures are triggered in case of any discrepancies.

PreviousTime Based OTPNextArchitecture

Last updated 1 year ago

Was this helpful?