Per-application MFA / step-up at OAuth authorization time · Issue #160 · authify/authify · GitHub
Skip to content

Per-application MFA / step-up at OAuth authorization time #160

Open

Description

@jgnagy-hermes

Description

MFA is enforced at session login only. An OAuth application cannot demand a fresh MFA challenge before issuing an authorization code. There is no per-app MFA policy.

Rationale (roadmap: hermes-j33, P1)

Auth0 and Okta both support per-app MFA policies and step-up. Identified in j33.4.

Suggested approach

  • Add a require_mfa flag (or mfa_policy) to the OAuth Application schema.
  • In OAuthController.authorize/2, if the app requires MFA and the user's last MFA challenge is older than a threshold (or absent), redirect to /mfa/verify with a return-to-authorize target.
  • Surface the policy in the consent screen.
  • Files: lib/authify/o_auth/application.ex, lib/authify_web/controllers/oauth_controller.ex, lib/authify/mfa/flow.ex, migration.

Effort

M

Activity

  1. added
    enhancementNew feature or request
    securitySecurity-related issues and improvements
    roadmapRoadmap-driven feature work (epic hermes-j33)
    on Jul 19, 2026
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

    enhancementNew feature or requestroadmapRoadmap-driven feature work (epic hermes-j33)securitySecurity-related issues and improvements

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions