Hello Heidi.

Thank you for the complete information provided in your post below.

I do not have any experience with the Tomcat SPNEGO Valve per se, but quite a bit of experience with Windows Integrated Authentication. To me, the symptoms that you describe below, do not really look like a problem at the Tomcat level, but more like a problem between the browser and the Windows authentication in general.

See notes and questions in the text below.

On 02.09.2019 12:35, Heidi Leerink - Duverger wrote:
We have the following problem with connecting from the tomcat environment 9.024 
with the
Active Directory of Windows, Kerberos database. (win2008 DC's)

In Tomcat's log files, with Tomcat8, which gives no problems, it is connected 
to the
Active directory.

It indicates that a login attempt is made 3 times whether the person can log in 
with the
Active directory account.

After that the login is accepted and qualified as successful.

In tomcat 9, different versions tried, also version 9.024, the control of 1 
becomes visible,

which is successful. But then the check is stopped (not 3 times as Tomcat8) and 
connection is marked as unsuccessful.

The environment for Tomcat9 is the same as from Tomcat8.

Q1: Are you sure that it is *exactly* the same ?
For example, do the tomcat8 installation, and the tomcat9 installation, run on the same server, and is the server *domain* the same in both cases ?

Q2: when "it does not work", does the browser popup a login dialog ?

Reason for the questions :
Typically, a succesful Windows authentication consists of indeed 3 exchanges (what you say happens with tomcat8).
The first of these exchanges consists of the browser requesting the original 
The server then responds with a 401 response ("need authentication"), in which it indicates that it wants an authentication, of the SPNEGO type. The browser then normally responds with a 2d request for the same URL, containing a partial "Authorization:" header containing some encrypted token. If the browser does NOT send this 2d request, it indicates that *the browser refuses* to do an SPNEGO authentication in this case. And that happens when the browser does not think that the server "can be trusted" for doing SPNEGO authentication. The browser will not trust the server, if it thinks that the server is not in the same domain as itself (unless you have manually added this server in the "trusted servers", at the browser level).

Q2: Usually, when the browser refuses to do a WIA authentication, it tries a Basic authentication instead, and this login dialog pops up. With Windows authentication, that is usually the first sign that something is not correct in the browser/server setup.

Note: I'm not saying that this IS your problem. But it is the first thing to verify, with WIA authentication.

To see this more clearly, you could try to install on the workstation, some software that allows you to trace the HTTP exchanges between the browser and the server (example : Fiddler2), and compare what happens with tomcat8 and tomcat9 (look at the HTTP headers for request/response).

Windows 10 PRO

Oracle database rdbms 11.203


Ords2019 - Oracle listener


Tried both java versions:

E:\java\jre64b\bin>java -version

java version "1.8.0_202"

Java(TM) SE Runtime Environment (build 1.8.0_202-b08)

Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode)


E:\java\openjdk\bin>java -version

openjdk version "11.0.1" 2018-10-16

OpenJDK Runtime Environment 18.9 (build 11.0.1+13)

OpenJDK 64-Bit Server VM 18.9 (build 11.0.1+13, mixed mode)

Tomcat 9.024 directory structure.

( log files in the attachments )




<?xml version="1.0" encoding="UTF-8"?>


   <Valve className="org.apache.catalina.authenticator.SpnegoAuthenticator"



   <Realm className="org.apache.catalina.realm.JAASRealm"









     com.sun.security.auth.module.Krb5LoginModule required











      default_realm        = U4AGR.COM

      default_tkt_enctypes = rc4-hmac aes256-cts-hmac-sha1-96 

      default_tgs_enctypes = rc4-hmac aes256-cts-hmac-sha1-96 

      permitted_enctypes   = rc4-hmac aes256-cts-hmac-sha1-96 

      dns_lookup_kdc = true

      dns_lookup_relam = false


      U4AGR.COM = {

         kdc = u4agr.com

         default_domain = U4AGR.COM



.u4agr.com= U4AGR.COM

u4agr.com= U4AGR.COM



Creation statement for tomcat.keytab:

ktpass /out c:\Temp\tomcat.keytab /mapuser DECADE_SSO_TC.U4AGR.COM /princ
HTTP/nlsl-decadetst.u4agr....@u4agr.com /pass "D3cad3401" /kvno 0 -ptype 

ktpass /out c:\temp\1c-tomcat.keytab /mapuser DECADE_SSO_TC.U4AGR.COM /princ
HTTP/nlsl-decadetst.u4agr....@u4agr.com /pass "D3cad3401" -crypto All /kvno 0 























*Met vriendelijke groeten van***

*Heidi Leerink - Duverger*
*Technisch Consultant*

In business for people.

*Unit4 Business Software Netherlands B.V.*
Papendorpseweg 100, 3710 BJ Utrecht, Netherlands

*T *+31 88 247 1444
*E *heidi.duver...@unit4.com

This message and any attachment(s) are intended only for the use of the named 
and may contain information that is privileged, confidential or otherwise 
exempt from
disclosure under applicable law. If you are not the intended recipient, please 
notify the
sender by return e-mail and delete this message from your system. Do not 
disclose the
contents of this document to any other persons. Violation of this notice may be 
Please note that internet communications are not secure and e-mails are 
susceptible to
change. Thank you for your cooperation.

To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to