yoge05
yoge05
Branch Unspecified
04 Apr 2012

jass kerberos login module for web application

I want my login.jsp to take the principal and password and authenticate against KDC, I hav written the code for login module but when i deploy my war file , The login page doesn't get loaded and when i see the tomcat catalina.out log file , I oobserved that its tomcat that is using kerberos login and not my web application, can anybody corret me?, am I doing something wrong

contents of catalina.out

Debug is true storeKey false useTicketCache false useKeyTab false doNotPrompt false ticketCache is null isInitiator true KeyTab is null refreshKrb5Config is false principal is null tryFirstPass is false useFirstPass is false storePass is false clearPass is false [Krb5LoginModule] user entered username: tomcat

Acquire TGT using AS Exchange [Krb5LoginModule] authentication failed Client not found in Kerberos database (6) - CLIENT_NOT_FOUND Authentication failed: Client not found in Kerberos database (6) - CLIENT_NOT_FOUND Apr 4, 2012 5:15:21 AM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8080 Apr 4, 2012 5:15:22 AM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Apr 4, 2012 5:15:24 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: A web application registered the JBDC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. Apr 4, 2012 5:15:24 AM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThread SEVERE: A web application appears to have started a TimerThread named [Timer-0] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled. Apr 4, 2012 5:15:24 AM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThread SEVERE: A web application appears to have started a TimerThread named [MySQL Statement Cancellation Timer] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled. Apr 4, 2012 5:15:24 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application appears to have started a thread named [http-8080-1] but has failed to stop it. This is very likely to create a memory leak. Apr 4, 2012 5:15:24 AM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080

Be the first one to reply

Share this content on your social channels -

Only logged in users can reply.