-
Improvement
-
Resolution: Fixed
-
Major
-
None
now when an issue happens with the token, session, user, time, ... Jenkins shows an Ooops exception that it is pretty annoying, so to avoid this kind of stuff that use to be resolved activating the force authentication, I will try to allow users to re-authenticate in case that the session, token, or other weird stuff happens by invalidating the session and redirecting the user to the IdP. Also I will improve the error messages to point admins to the guides and to more specific errors.
- is related to
-
JENKINS-54275 (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old
- Resolved
-
JENKINS-44992 SamlException after metadata update
- Resolved
-
JENKINS-48030 SAML Azure AD exception
- Resolved