Jama Connect User Guide

Authentication methods

Jama Connect supports a wide range of authentication methods to keep your data safe and secure by authenticating users. The default method, Basic authentication, verifies users with the login data that is stored in the Jama Connect database. However, different integrations are available for cloud or self-hosted environments.

auth_types.png

Supported combinations for self-hosted and cloud

  • SAML for SSO and OAuth for REST

  • Multi-mode for user authentication and OAuth for REST

For information about using the Jama Connect REST API with OAuth, see Set API credentials.

Supported third-party authentication methods

  • SAML — Cloud and self-hosted option. Open standard for transferring identity data between two parties: an identity provider (IdP) and a service provider (SP).

    Electronic signatures are enabled by default, but can be disabled by a system administrator.

    To set up SAML, your company must meet these requirements:

    • Have a SAML 2.0-compliant Identity Provider (IdP).

    • Identify a technical person, often an IT administrator, who can provide the URL of the Identity Provider. Name this person before engaging with Jama Software and, for testing purposes, provide them access to Jama Connect.

    • Cloud customers — You must contact support to schedule enablement.

    • Self-hosted customers — If you're on a version of Jama Connect earlier than 8.62, you must follow instructions for that release instead of the instructions here. Contact support for help accessing the correct instructions and with the process.

  • LDAP — Self-hosted option. Centralizes the management of user accounts. Jama Connect includes a built-in integration of LDAP and Microsoft Active Directory.

  • Crowd — Self-hosted option from Atlassian. Manages users and groups within a single a system. Jama Connect accepts user details from Crowd, then syncs them with authentication data in the application.

Internal authentication methods

  • Basic — The default authentication for Jama Connect. Basic authentication uses a username and password that’s stored in the Jama Connect application database.

  • Basic + IdP — The combination of Basic and SAML creates multi-mode authentication, so you can separate your internal users from your external partners, vendors, and contractors. Multi-mode authentication provides access for external users so they can be part of the requirement, approval, and tracking process in Jama Connect.

    Note

    To use multi-mode authentication, you must be running Jama Connect 8.62 or later.

As a self-hosted user, you can update or change the authentication type for an organization. To do this, log in as root user and select System Properties > Authentication Properties.