FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login
    1. Home
    2. mgetka
    3. Topics
    M
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 44
    • Best 21
    • Controversial 0
    • Groups 1

    Topics created by mgetka

    • M

      Unsolved Friction-free multi application SSO with MFA enabled

      Q&A
      • mfa sso oauth2 • • mgetka
      5
      1
      Votes
      5
      Posts
      7.4k
      Views

      joshuaJ

      @dan Also, depending on the workflow, if a user does NOT federate but does NOT check "trust this computer" they will NOT establish "MFA trust". Without trust, a user will be prompted to MFA again. Of couruse, With "MFA trust", they will not be prompted. This answer is implicit to this conversation, but MFA policies and FusionAuth center around this check box and trust (with the current edge case of Federation noted).

    • M

      Authorization lambda?

      General Discussion
      • • • mgetka
      3
      0
      Votes
      3
      Posts
      3.6k
      Views

      M

      Ok, I've created a feature request.

    • M

      How to determine if an user has a password?

      Q&A
      • • • mgetka
      3
      1
      Votes
      3
      Posts
      1.6k
      Views

      K

      @dan Hello, reaching out to know if this still the same, ie no way to know whether an user has a password or not?

    • M

      What happens after asymmetric key expiration?

      Q&A
      • • • mgetka
      7
      1
      Votes
      7
      Posts
      7.5k
      Views

      danD

      Well, since we're talking about behavior based on a fix that isn't written yet, things are a bit theoretical. 🙂

      Here's one approach we'd consider. An expired key pair cannot be used to sign a JWT, so we would either have to generate a new key pair ahead of the expiration, or start failing login operations. The former is a better user experience, so a user will either have to regenerate the key, or we would do it based upon a configured policy.

      Also, wanted to be clear that we are aware of this limitation, which is why we set the default expiration period to 10 years (so we have a bit of time to solve this in the best way possible).

      Hope this helps. Let me know if you don't have the information you need.