My application runs under tomcat. It uses the GSS API (JNDI) to connect to the Active Directory LDAP server using Kerberos. It allows the user to define AD servers and try to connect to them. However, as soon as the first Kerberos attempt using the connection attempt is completed, the application will not read the Kerberos ( /etc/krb5.conf) configuration again . Therefore, any change in it requires a restart of tomcat.
How can I avoid such a restart? How to force an application to reload Kerberos configuration before each connection attempt?
source
share