Skip to content

[BUG]: late validation of refresh_tokens #54

Description

@ayush00git
  • refresh_tokens for now are being saved to db just after a successful login, which for now does not covers mfa, as the server now supports mfa as well, so while logging in, access and refresh tokens would be sent to client on the basis of mfa_type associated with his account.
  • And try revolving the design around users table for inspecting mfa_type, for now the design revolves around mfa_secrets table for this.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions