-
Suggestion
-
Resolution: Unresolved
-
Low
-
None
-
None
-
None
-
None
Problem Definition
Currently, Assertion Consumer Service URL and Audience URL are hardcoded to be the base URL for the instance.
Suggested Solution
Allow the Assertion Consumer Service URL to be configurable via
- Application SAML UI
- Application REST API
Why this is important
Setting up SAML for 100+ Atlassian instances is a pain as it requires new Entity ID for each integration. Having configurable Assertion Consumer Service URL helps to reduce the number of Entitiy ID configured associating to Atlassian applications in the SAML provider.
Workaround
None
- mentioned in
-
Page Failed to load
[SAMLDC-41] Allow configuration of Assertion Consumer Service URL
Workflow | Original: SAMLDC Workflow v2 [ 2404654 ] | New: JAC Suggestion Workflow 3 [ 4271281 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 595809 ] |
Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |
Status | Original: Verified [ 10005 ] | New: Open [ 1 ] |
Description |
Original:
h3. Problem Definition
Currently, Assertion Consumer Service URL and Audience URL are hardcoded to be the base URL for the instance. h3. Suggested Solution Allow the Assertion Consumer Service URL to be configurable via * Application SAML UI * Application REST API h3. Why this is important Setting up SAML for 100+ Atlassian instances can be a pain as it requires new Entity ID for each integration. h3. Workaround _None_ |
New:
h3. Problem Definition
Currently, Assertion Consumer Service URL and Audience URL are hardcoded to be the base URL for the instance. h3. Suggested Solution Allow the Assertion Consumer Service URL to be configurable via * Application SAML UI * Application REST API h3. Why this is important Setting up SAML for 100+ Atlassian instances is a pain as it requires new Entity ID for each integration. Having configurable Assertion Consumer Service URL helps to reduce the number of Entitiy ID configured associating to Atlassian applications in the SAML provider. h3. Workaround _None_ |
Description |
Original:
h3. Problem Definition
Currently, Assertion Consumer Service URL and Audience URL are hardcoded to be the base URL for the instance. h3. Suggested Solution Allow the Assertion Consumer Service URL to be configurable via * Application SAML UI * Application REST API h3. Why this is important Setting up SAML for 60+ Atlassian instances can be a pain as it requires new Entity ID for each integration. h3. Workaround _None_ |
New:
h3. Problem Definition
Currently, Assertion Consumer Service URL and Audience URL are hardcoded to be the base URL for the instance. h3. Suggested Solution Allow the Assertion Consumer Service URL to be configurable via * Application SAML UI * Application REST API h3. Why this is important Setting up SAML for 100+ Atlassian instances can be a pain as it requires new Entity ID for each integration. h3. Workaround _None_ |
Status | Original: Open [ 1 ] | New: Verified [ 10005 ] |