Darwin Felix

1) 302 server redirects 2) spnego.authz.403 page 3) isEmtpy() with isBlank() 4) Base64 @Deprecated 5) Fixed: getLocalAddr() causing NPE 6) Added IAM Gateways support

Hi Kei, I'm glad everything is now working as expected. Yes, 14 years is a long time but I'm always happy to help. Thanks, -Darwin

Hi Kei, > checking the AES128 or AES256 settings in the Active Directory Users and Computers program, > it gives me the KDC has no support for encryption type (14) error. > Leaving them unchecked gave me the Connection test successful message. Do you mind leaving AES128 and AES256 checkboxes un-checked for right now? > forwardable = true > defaultrealm = DOMAIN-NAME.LOCAL > defaulttktenctypes = aes128-cts aes256-cts rc4-hmac des3-cbc-sha1 des-cbc-md5 des-cbc-crc > defaulttgsenctypes = aes128-cts...

Hi Kei, Thank you for taking a look at this library to see if it might be helpful for your project. I also thank you for providing all of this info right upfront. > Also I have the app and AD/KDC on the same machine (Windows Server 2012) I've never tried this config and I'm not 100% sure if it will work or not. Are you able to put the app on a 3rd machine instead? Also, do you mind specifying which JDK vendor and the JDK version you are using? Thanks, -Darwin

Hi Maarten, I have not tried it with that JDK. Are you aware of any API changes or available encryption algorithms that might make it troublesome? Thanks, -Darwin

Hi Maarten, I'm sorry to hear that you are still stuck with your configuration. Perhaps, the best thing to do now is to start over with a hello world example. I don't really have any better suggestions or any more ideas of what the issue might be in your setup/environment. Looks like Ssu gave some good ideas and maybe continue to pursue those as well. Just to be sure, I went ahead and tried to re-create the problem again in our network. Here are the steps I took: 1) Created a new pre-auth account...

FYI. Added two (2) new examples/guides on https://spnego.sourceforge.net/ The package names of the servlet-api is migrating from javax.servlet to jakarta.servlet. Spring Boot 2.x still uses the javax.servlet package name whereas Spring Boot 3.x now uses the jakarta.servlet package name. If you are on Spring Boot 2.x, you can continue to use the spnego-r9.jar file. However, if you want to use Spring Boot 3.x, you will have to use the spnego-jakarta-2.0.jar file. Both jar files can be download here......

Hi Maxime, https://sourceforge.net/projects/spnego/files/ I tested the spnego-r9.jar with Java 11 and it worked. Tomcat 8 and Java 8 => worked Tomcat 9 and Java 11 => worked However, spnego-r9.jar did not work with Tomcat 10. Tomcat 10 and Java 11 => did not work So, I updated the SPNEGO source-code and created spnego-jakarta-2.0.jar. I tested spnego-jakarta-2.0.jar with Java 11 and it worked. Tomcat 10 and Java 11 => worked Btw, in the meantime, I also made a couple of minor changes. I attached...