# Automatic Authentication Issue After Jenkins and Tomcat Upgrade

**URL:** <https://community.jenkins.io/t/automatic-authentication-issue-after-jenkins-and-tomcat-upgrade/37259>\
**Category:** Community\
**Created:** [September 8, 2026, 11:41am UTC](https://community.jenkins.io/t/automatic-authentication-issue-after-jenkins-and-tomcat-upgrade/37259 "2026-09-08T11:41:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Neha1](https://avatars.discourse-cdn.com/v4/letter/n/e68b1a/32.png) [@Neha1](https://community.jenkins.io/u/Neha1)\
**Post date:** [September 8, 2026, 11:41am UTC](https://community.jenkins.io/t/automatic-authentication-issue-after-jenkins-and-tomcat-upgrade/37259/1 "2026-09-08T11:41:24Z")

</div>

We were previously running Jenkins **2.462.1** on **Tomcat 9**. We have integrated our internal IdP ( **Alfa** ) using configurations in `web.xml` along with some supporting libraries. With this setup, when users accessed the Jenkins URL, they were automatically authenticated and logged in through Alfa.

After upgrading Jenkins to **2.528.3** and migrating to **Tomcat 10** , the automatic authentication is no longer working. Users are now presented with the Jenkins login page and must manually click the **“Sign In”** button to authenticate.

Could you please let us know if there are any configuration changes required in Jenkins 2.528.3 or Tomcat 10 that could impact this behavior? Are there any additional settings, compatibility requirements, or migration changes that we need to consider to restore automatic SSO authentication?

_ **Note:- Jenkins version 2.462.1 is not supporting tomcat 10 and jenkins version 2.528.3 is not supporting tomcat 9.** _

Thanks in advance for your guidance.

Regards,  
**Neha**