SSL handshake errors filling up tomcat logs despite not enabling any level of IDP logging

  • 7013262
  • 12-Sep-2013
  • 18-Sep-2013


NetIQ Access Manager 3.2
NetIQ Access Manager 3.2 Support Pack 2 applied
NetIQ Access Manager 3.2 Identity Server
Users accessing protected resources requiring X509 authentication and simple Name/Password based Authentication


Access Manager 3.2.2 setup and running fine. The identity server is running on a SLES 11 SP2 64-bit, fully patched server.
Multiple contracts including X509 and Secure Name Password enabled on the Identity Server.

Users, when their browsers are properly pre-configured with a User certificate, are able to login just fine using client certificates. However, when a browser without any imported client certificates on any device type tries to access a site secured with that x509 method, even when the IDP "Component File Logger Levels" are all set to off or info, multiple Java exceptions are written to the catalina.out file. With this site potentially getting 1000s of hits a day, concerns were raised about the content of the catalina log files.

Ideally, if the browser doesn't have a User certificate to hand back, we just need print a single line or two of a properly handled/worded error message. Here's the message that is reported back ...

Mar 22, 2013 1:57:27 PM handShake INFO: Error trying to obtain a certificate from the client handshake alert: no_certificate at at at at at at at at at org.apache.coyote.http11.Http11Processor.actionInternal( at org.apache.coyote.http11.AbstractHttp11Processor.action( at org.apache.coyote.Request.action( at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( at sun.reflect.DelegatingMethodAccessorImpl.invoke( at java.lang.reflect.Method.invoke(


Fixed in 3.2.2 IR1.

Additional Information

The /opt/novell/nam/idp/conf/ file was changed to remove this.