Multi-Factor Authentication (MFA) in Jama Connect: SSO vs Basic Authentication

Published Date: April 23, 2026
Validated: Yes
Audience: Everyone
Products and Versions Covered:

Jama Connect® version(s)
- Cloud/CVC
- Self-hosted

Summary

This article explains how multi-factor authentication (MFA) works in Jama Connect.

MFA is supported when authentication is managed through a SAML-based single sign-on (SSO) configuration and enabled in the organization’s identity provider (IdP). In this setup, MFA is enforced outside of Jama Connect during the login process.

MFA is not supported for users who sign in using basic authentication (username and password), including environments where both SSO and basic authentication are enabled (multi-mode). This limitation exists because basic authentication is handled directly within Jama Connect and does not integrate with external MFA controls.

Resolution

Enable MFA Through SSO (SAML)

Configure SAML-based SSO in Jama Connect and ensure MFA is enabled in your identity provider (IdP). Once configured, users authenticating through SSO will be prompted for MFA based on your IdP settings.

Manage Users on Basic Authentication

Users logging in with basic authentication will not have MFA protection. To enforce MFA, transition these users to SSO-based authentication where possible.

Best Practice

For improved security, use SSO with MFA enabled in your identity provider and limit or disable basic authentication where feasible.

Additional Resources (for all external articles)

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

Related to