Remy, > > P.S.: I'm also +1 for removing the CertificatesValve, since it is > > confusing to have several valves essentially doing the same thing. > > There's no need to hardcode the authenticator, you only need to add it > in startup.Authenticators.properties, and it will be added in the > pipeline as needed. It's already there, BTW, so I don't quite see what's > going on (but it should be fixed there, no harcoding required).
yes, I understand. The confusing part was that in ContextConfig, we were adding both the CertificatesValve (in certificatesConfig) and the Authenticator configured in web-app/login-config/auth-method, where CertificatesValve and SSLAuthenticator were essentially doing the same, except that CertificatesValve was operating on the (SSL)Socket and was always failing on a CoyoteRequest (whose getSocket() always returns null). Bill has cleared up this confusion by removing the certificatesConfig() method. Thanks, Jan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
