Just a follow up that we got this working using Locations and url patterns. After enabling both mod_ssl (with client certs) and mod_authnz_ldap, we do <Location /secure/cert/ > and <Location /secure/ldap/ > each doing it's own flavor or authentication, then reverse proxying both requests to our app server ProxyPass http://localhost:8080/ ProxyPassreverse http://localhost:8080/ Jeff jblack4 wrote: > > Not sure if this is possible with a single apache server instance, so I'm > curious if anyone has done this. We want apache to be configured to be > single public entry point into our private web services. Additionally, we > want users to be able to login based on a user/pass or a client > certificate. The user/pass would validate against an Active Directory > server with mod_auth_ldap. The client cert path would be handled with ssl > mod. > > So the question is can this be accomplish in a single apache, or do I need > one for each authN mechanism? Anyone running this kind of setup that > could share any tips? > > Thanks, > > Jeff > -- View this message in context: http://www.nabble.com/Dual-authN-path-with-client-certs-and-ldap-tp19373244p19671831.html Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|