[us...@httpd] Authenticate only once for IP address or DNS name or alias

2009-04-01 Thread jblack4
I have Digest authentication working if the user enters IP address in the browser. If that application then makes a request for data to either the fully qualified DNS name or intranet alias (of that same server), the user gets prompted again for username and password. Is there a way to make the

Re: [us...@httpd] exclude errorDocument from authentication

2009-03-03 Thread jblack4
This does not seem to work for some reason. I tried putting the override section above, then below the authenticated section, but always got the standard 401 page versus the custom register.html page. It also appeared that maybe the proxy configuration of one location is being applied to both.

[us...@httpd] exclude errorDocument from authentication

2009-02-27 Thread jblack4
Given that I have a locked down with authentication and that I want a custom "ErrorDocument 401 /register.html", how can I exclude the /register.html page from the authentication location pattern? -- View this message in context: http://www.nabble.com/exclude-errorDocument-from-authentication-t

[EMAIL PROTECTED] [EMAIL PROTECTED] verse proxy and consistant URL for two public entry points

2008-09-25 Thread jblack4
Curious how this could be accomplished, I have tried several ideas using url rewrite and proxying, without the desired effect. I have two URL Locations specified in httpd.conf, but want to reverse proxy them both to the same location. We haave this working currently. The trick now is to make th

Re: [EMAIL PROTECTED] Dual authN path with client certs and ldap

2008-09-25 Thread jblack4
: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. A

[EMAIL PROTECTED] Dual authN path with client certs and ldap

2008-09-08 Thread jblack4
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.