Resolve “Authentication Service Is Not Configured” for SAML SSO in Self-Hosted (KOTS) Jama Connect®

Published Date: June 1, 2026
Audience: Everyone
Products and Versions Covered: 

• Jama Connect® version 9.28 and above
  • Cloud/CVC
  • Self-hosted

Summary

This article explains how to recover SAML SSO in a self-hosted, Jama Connect® environment when authentication stops working and users see errors such as java.io.IOException: Error: Authentication service is not configured in the contour.log.

Resolution

1. Re-Enter SAML metadata in Root Menu

   • In the Jama Connect® SAML configuration, paste the full metadata XML into the Metadata XML field (or Metadata URL), then save.

2. Delete core statefulsets, SAML/OAuth deployments, and related PVCs

   • On the application server, run the following command:

   kubectl delete sts/core sts/hazelcast sts/activemq deploy/saml deploy/oauth pvc/volume-saml-0 pvc/volume-oauth-0

3. Re-deploy from the KOTS Admin Console

   • In the KOTS Admin Console, redeploy the latest saved configuration/sequence using the Redeploy action. 

4. Confirm resolution

   • Verify saml and oauth pods return to a healthy Running state.
   • Test SAML login

Additional Resources 

• Success Programs
• Success Catalog
• Datasheets
• Request a Solution Offering or Training from the Success Catalog

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