Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Not able to login JIRA after upgrade to 9.15.2 and date import from another environment(PROD)

Shashank Aman
June 10, 2024

Here are the logs :

ERROR anonymous 942x106x1 - 10.164.118.219:58954,10.164.72.6 /plugins/servlet/samlconsumer [c.a.p.a.s.web.filter.ErrorHandlingFilter] [UUID: ede4367d-2ab9-4ff7-891a-5dde9b99ab4a] Received invalid SAML response: Signature validation failed. SAML Response rejected
com.atlassian.plugins.authentication.sso.web.saml.provider.InvalidSamlResponse: Received invalid SAML response: Signature validation failed. SAML Response rejected
  at com.atlassian.plugins.authentication.sso.web.saml.provider.impl.OneloginJavaSamlProvider.lambda$extractSamlResponse$1(OneloginJavaSamlProvider.java:97)
  at com.atlassian.plugin.util.ContextClassLoaderSwitchingUtil.runInContext(ContextClassLoaderSwitchingUtil.java:48)
  at com.atlassian.plugins.authentication.sso.web.saml.provider.impl.OneloginJavaSamlProvider.extractSamlResponse(OneloginJavaSamlProvider.java:88)
  at com.atlassian.plugins.authentication.sso.web.saml.SamlConsumerServlet.doPost(SamlConsumerServlet.java:98)

Please suggest us some solution to solve it.

Thanks

1 answer

0 votes
Matt Doar _Adaptavist_
Community Champion
June 10, 2024

If you are using the built-in SAML config page, the values are different for prod and non-prod instances. You would need to log in as a non-SAML admin and update the SAML settings for that environment back to what they were before.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events