MySQL Restore of .jama Missing SAML and OAuth Data

Carmen Santos
Carmen Santos
  • Updated

Published Date: May 4, 2026
Audience: Everyone
Products and Versions Covered: 

  • Jama Connect® - all versions
    • Cloud/CVC
    • Self-hosted
  • Database MySQL

Summary

When restoring a .jama backup, SAML and OAuth data is not included in the restore in environments using MySQL. This happens because, in MySQL deployments, SAML and OAuth are stored in separate databases, while the .jama backup file only contains the main Jama Connect database (in XML format) along with assets such as attachments and reports.

As a result, restoring a .jama file will not bring back SAML and OAuth data. These must be handled separately to ensure a complete system restoration.

In contrast, in Microsoft SQL Server (MSSQL) environments, all data resides within a single database (organized into schemas). In those cases, SAML and OAuth data is included in the .jama backup and restored automatically.

Resolution

To ensure SAML and OAuth data is retained during a restore, create separate database dumps for both before performing the backup. If SAML is enabled, disable it before taking the backups. 

After restoring the .jama file, manually restore the SAML and OAuth databases. After the process is complete, re-enable SAML.

Additional Resources 

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

Related to

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.