Author: Erik Haake
Date: October 31st, 2025
Audience: Everyone
Environmental Details:
- Self-hosted, Replicated - KOTS
- All supported versions
Summary
If, after logging into Jama Connect®, you are redirected to the login page without being presented with an error, then you may be encountering a redirection login loop. This can be verified by opening the Network tab in your Browser's developer tools and logging in again. If you click on the network request for <your-hostname> and check the Headers, you will see a Status Code of '302 Found'. You can also verify if you were successfully authenticated by selecting the 'login.req' request and viewing the Status Code. If it is 200 OK, then your login was successful and Jama Connect® is working correctly.
In this case, what is happening is that TLS is not enabled in your current configuration. The session cookies sent by Jama Connect require their transmission over an HTTPS connection and will otherwise not be stored by the browser. This means that even though your credentials were successfully authenticated, your browser is not presenting a valid session to Jama Connect, and you are being redirected to the login page.
Solution
- Enable TLS in the Jama configuration in the KOTS admin console.
- Save the configuration and redeploy the new sequence.
Cause
The login issue is caused by a browser redirection after successful authentication due to TLS not being enabled in the Jama configuration. Jama session cookies not sent over HTTPS connections will not be stored by the Browser.
Prevention
Ensure TLS is enabled in the Jama configuration before deployment. Regularly check for updates and follow best practices for server configuration to avoid similar issues.
Additional Information / Metadata /Resources
- Login redirection, 302 (Found) status code, TLS, HTTPS
Feedback:
Have suggestions or improvements? Please leave your feedback in the comments section below.
Comments
0 comments
Please sign in to leave a comment.