Known issues and limitations

When a user logs into Jira from the Logout screen, using the Login link in the top right navigation, the user is successfully logged in, but the user is prompted with a Logout confirmation dialog upon login.

The prerequisite before performing SSO is that a valid user must exist in both the IdP and the Atlassian product. In a scenario where a user exists for an IdP but does not exist in the Confluence server, an SSO attempt will result in an error message for Jira and Confluence.

The PingFederate server will perform a CRL check of the certificate received by the Authenticator class. If PingFederate cannot connect to the CRL server to verify the certificate this can cause a delay during SSO. To remove this delay make sure that the PingFederate server can resolve the CA that issued the certificate by using DNS or a adding entries to the hosts file that resolve the CA server.

The kit can’t be used with the built in SAML SSO that comes with the Atlassian applications. The user will be asked to log in twice in some cases, or the Atlassian integration kit will take over the login method for SAML SSO.