...
| Info | ||
|---|---|---|
| ||
These configurations are examples working with our lab environment. We cannot guarantee that these configurations are suitable for your environment. We can support IdP configuration on best effort basis only, but feel free to contact us at atlassianplugins@resolution.de. In most cases, we can help you |
General Information
SAML SingleSignOn currently implements a subset of the SAML standard:
- HTTP POST is the only supported binding
- The Confluence/JIRA userid must match the NameID-attribute in the SAML Response. It can be transformed with a Regex in the plugin configuration e.g. to remove the domain-part of an email address if the userid is the name-part
- The SAML request is neither signed nor encrypted
- Encrypted SAML-responses are not supported
- Within the SAML-response, the Assertion must be signed (signing the response itself is not sufficient (
).Jira Legacy server JIRA (resolution.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 996ec45d-74a1-3c85-a5bc-f20f070079ab key SSSO-6
Example Configurations
| Child pages (Children Display) |
|---|