Author: Sravya Bandari
Date: Nov 17th 2023
Audience: Everyone
Environmental details: Setting up SAML for self-hosted customers
Summary:
This guide provides an overview of enabling or configuring SAML for on-premises customers using version 8.62 and above.
The SAML service will run locally in self-hosted instances on version 8.62 and above. Users should be able to configure and use SAML as long as the SAML container runs.
Steps:
Jama version 8.62 and above:
Customers will need to input the following information into their IDP for configuration.
Audience URL (Entity ID):https://[HOSTNAME]/saml/metadata/alias/defaultAlias
Reply/Assertion Consumer Service URL:https://[HOSTNAME]/saml/SSO/alias/defaultAlias (Note: The hostname is case-sensitive.)
Unique identifier for the user: Jama matches the email address, so the Unique User Identifier's 'name identity format' should be 'unspecified,' and the source attribute should be the user's Email.
- Please follow the below steps once the configurations are done on IDP:
- Pull the new metadata from IDP as either XML or URL
- Enter the new metadata into Jama. Set the first and last name properties.
- Hit save and test it out.
- If a connection is established, the last three fields in that view will be auto-populated as follows,
SP metadata URL: https://[HOSTNAME]/saml/metadata/alias/defaultAlias
ACS / single-sign-on URL: https://[HOSTNAME]saml/SSO/alias/defaultAlias
SP entity ID / Audience restriction:https://[HOSTNAME]/saml/metadata/alias/defaultAlias
Related to
- Authentication
- Relationships
- Administration
- Testing
- REST API and extensibility
- Reports
- Microsoft Word
- Microsoft Excel
- Installation
- Migration
- Coverage and traceability
- Traditional
- Jama Connect Interchange™
- Customer-Validated Cloud
- Security
- Diagram/Graph Editor
- Jama Software® Subscriptions Maintenance and Support Service Agreement
- Jama Connect®
- Supported
- Item Configuration
- Deployment Migration
- Integrations
Comments
0 comments
Article is closed for comments.