Hello,
We are using SAML single sign-on in Atlassian in our project. We have implemented SSO before 2 months ago and it was working properly on our development environment. Today we tried to test this feature but found that Jira SSO not working. After further investigation we found that the SAML version inside SAML-Request is changed to SAML2.0, but previously it was working on SAML1. Can you please advise is there any updates in JIRA related to this feature(SAML SSO)?
The SAMLRequest as per below:
Updated SAMLRequest :
<?xml version="1.0" encoding="UTF-8"?>
<saml2p:AuthnRequest xmlns:saml2p="urn:oasis:names:tc:SAML:2.0:protocol" AssertionConsumerServiceURL="https://auth.atlassian.com/login/callback?connection=saml-55d....." Destination="https://moody-liger-76.loca.lt/......" ID="_1d87dea....." IssueInstant="2022-04-18T10:33:44.504Z" ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Version="2.0">
<saml2:Issuer xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion">https://auth.atlassian.com/saml/55d9d80c-c68c-49b4-b817-c2e06238d471</saml2:Issuer>
<saml2p:NameIDPolicy AllowCreate="true" Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress" />
</saml2p:AuthnRequest>
OLD SAMLRequest had tags like :
<samlp:AuthnRequest> </samlp:AuthnRequest>
<saml:Issuer> </saml:Issuer>
If there is any updates on SSO, can you please share the details?
Thank you.
Hello, @Namrata Desai
As far as I am aware Atlassian's SAML SSO app never supported SAMLv1.
Nothing in the sample you've presented suggests that the old request was SAMLv1. You may be confused by the difference in element namespaces (prefixes) being "samlp" vs. "saml2p" but the actual string value of the namespace name is irrelevant for XML parsing.
If it "stopped" working the problem is elsewhere e.g. a change or expiry of the certificate. Dig into the logs – surely there must be errors logged in there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.