-
Notifications
You must be signed in to change notification settings - Fork 619
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SAML SSO Option: forceAuthn #1417
Comments
Currently there is not config.json setting for this, but I can add it. In this case, the default is probably false already. If you want, I can add a setting for this. You can go in the code now and test any option you like by adding things to "options" at this location. |
Gotcha. I'm still trying to debug why this 1 saml application requires re-auth and thought it might be that. I'll test and let you know. |
@Ylianst I need an option for this: With ADFS, you want this to be true in order for SSO to not require re-authentication. See: https://github.com/bergie/passport-saml Not everyone is using ADFS, so I recommend it be an option in the SAML portion of the config. |
Nice! Thank you for that research, I would have never been able to find that. I added the new option in the sample-config-advanced.json. You have to remove the "_" and it should work. Will be in v0.5.47 when it's next published.
|
Working perfectly! |
From: https://github.com/bergie/passport-saml
forceAuthn: if set to true, the initial SAML request from the service provider specifies that the IdP should force re-authentication of the user, even if they possess a valid session.
Is there a variable in mesh config that I can use to set this to false? Scanning through the code I see exactly 3 places this is mentioned - in the saml.js, in the readme.md, and in the passport-saml\test\tests.js
The text was updated successfully, but these errors were encountered: