RE: Web Publishing Authentication...
- From: "Ball, Dan" <DBall@xxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Wed, 18 May 2005 20:41:56 -0400
I've gone over this time and time again, it is still not working
properly. I've checked the logs on the webserver also, the requests are
showing the original client IP, so we know that part is working. Is
there anything else that I could check on the ISA server?
-----Original Message-----
From: Ball, Dan [mailto:DBall@xxxxxxxxxxx]
Sent: Wednesday, May 11, 2005 21:12
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Web Publishing Authentication...
http://www.ISAserver.org
Okay, I think that's the way it's set right now but I'll check it again.
-----Original Message-----
From: Jim Harrison [mailto:Jim@xxxxxxxxxxxx]
Sent: Wednesday, May 11, 2005 14:24
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Web Publishing Authentication...
http://www.ISAserver.org
Since your web server is using IPs to determine "locale", you need to
configure the web publishing rule as "Requests appear to come from the
original client" in the "To" tab.
-----Original Message-----
From: Ball, Dan [mailto:DBall@xxxxxxxxxxx]
Sent: Wednesday, May 11, 2005 9:01 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] Web Publishing Authentication...
http://www.ISAserver.org
I have been playing around with this for quite awhile now, and still
can't figure it out.
I have a .NET application running on an internal webserver that supports
LDAP(Active Directory) authentication for user accounts. It works
great, in that when a user connects to it from the internal network, it
automatically authenticates them, and logs them in.
However, a problem arises when someone from the Internet connects to
that webserver. The software is supposed to determine automatically if
it is a local connection or a remote connection and decide whether to
log them in or not. But instead of just connecting to the webserver
anonymously, it prompts them for a password. If you click "cancel" on
the login, and go back to that URL, it will then work properly.
Anyone have any ideas on how to set up the web publishing so that the
software will recognize it as an external connection in ISA2004?
Other related posts:
