SAML Configuration for Jama Connect® Cloud: Supported Signing Algorithms and Required Attributes

Amanda Jennewein
Amanda Jennewein
  • Updated
  • Jama Connect® version(s)
  • Cloud/CVC

Summary

This article provides clear guidance for completing security questionnaires related to Security Assertion Markup Language (SAML) configuration in Jama Connect® Cloud. It explains the supported signing algorithms for SAML authentication and responses, as well as the required user attributes for successful authentication.

Jama Connect® uses secure, modern SAML standards and requires a minimal set of user attributes to correctly identify and provision users. Questions typically arise when configuring an identity provider (IdP) or validating compliance with security requirements.

By the end of this article, readers will understand:

  • Which SHA-2 signing algorithms Jama Connect® supports
  • How Jama Connect® signs SAML authentication requests
  • Which user attributes are required and how they are used

Resolution

1. Supported SAML Response Signing Algorithm

Jama Connect® accepts SAML responses signed using SHA-2 certificates with RSA-SHA256.

This is the standard and recommended configuration for secure SAML integrations. Ensure your identity provider (IdP) is configured to sign SAML responses using RSA-SHA256.


2. SAML Authentication Request Signing (from Jama Connect®)

SAML authentication requests generated by Jama Connect® (when request signing is enabled) are signed using RSA-SHA256.

Configure your identity provider (IdP) to accept RSA-SHA256 signed authentication requests to ensure compatibility.


3. Required SAML User Attributes

Jama Connect® requires specific user attributes in the SAML assertion to successfully authenticate and match users.

Required attributes:

  • Email (used as NameID)
  • First Name
  • Last Name

Attribute requirements and usage:

  • The NameID must contain the user’s email address
  • The email serves as the unique identifier used to match the user in Jama Connect®
  • First and last name are required to populate the user profile and support proper user identification within the application

Ensure these attributes are included and correctly mapped in your identity provider (IdP) configuration.

Additional Resources

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.