Author: James Ressler
Date: October 16, 2023
Audience: Everyone
Problem:
Auth0 SAML cannot work because the User Principle Name (UPN) in the Identity Provider (IDP) is not an email address or one that matches the email used in the users' Jama account.
How to Diagnose:
Ensure that the UPN (for Azure Enterprise ID) or the NameID (for Okta) are set up as email addresses. If you need help, follow the solution below.
Solution:
Change the required claim in the IDP from UPN to email.
Azure Entra ID (previously known as Azure Active Directory)
First, navigate to your Jama Connect enterprise application and select "Single sign-on" from the left sidebar. Edit "Attributes & Claims."
Next, under "Required claim," select the claim by clicking anywhere on that row.
This will bring up the "Manage claim" screen where we can edit the source attribute. Make sure that the "Name identifier format" field is set to "Email address" and that the "Source attribute" field is set to "user.mail" and then select "Save."
Okta
First, navigate to your enterprise application in Okta and select the "Sign On" tab.
Under "Credential Details," make sure the "Application username format" is set to "Custom" with the expression "user.email"
After updating those fields, test the changes by looking up a user assigned to the app.
Additional Documentation and Resources:
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.