Re: Windows authentication and availability
From: Paul Clement (UseAdddressAtEndofMessage_at_swspectrum.com)
Date: 10/14/04
- Next message: John Constant: "Re: You are about to be redirected to a connection that is not secure"
- Previous message: Eran Kampf: "Re: Security problem when dynamically creating directories"
- In reply to: howard_at_nospam.nospam: "Windows authentication and availability"
- Next in thread: howard_at_nospam.nospam: "Re: Windows authentication and availability"
- Reply: howard_at_nospam.nospam: "Re: Windows authentication and availability"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 14 Oct 2004 14:21:34 -0500
On Tue, 12 Oct 2004 14:25:02 -0700, "howard@nospam.nospam"
<howardnospamnospam@discussions.microsoft.com> wrote:
¤ We are currently deploying an ASP.Net intranet application to our WAN. The
¤ application uses integrated Windows authentication. At present, each time
¤ there is a post-back, our code gets the user’s credentials and queries to see
¤ whether the user is a member of certain Active Directory groups.
¤
¤ In order to improve availability in various disaster scenarios, we deploy
¤ the application to a separate server at each of our 25 physical locations
¤ around the country. There is also a separate domain controller at each
¤ location. The idea is that even if the WAN fails, our application can still
¤ run, provided that the local network is still up.
¤
¤ I have two questions regarding availability in various disaster recovery
¤ scenarios.
¤
¤ 1. If the local domain controller fails, will post-backs fail because of our
¤ use of integrated Windows authentication?
¤
Not if you have a backup domain controller by which authentication can occur with respect to
resource access.
¤ 2. Each time we query the user’s credentials, are round-trips to the domain
¤ controller involved, or do the credentials get cached somewhere? We would be
¤ willing to assume that the user's credentials don't change during a single
¤ ASP.Net session.
Credentials (user ID and password) are cached at the browser level on the client.
Paul ~~~ pclement@ameritech.net
Microsoft MVP (Visual Basic)
- Next message: John Constant: "Re: You are about to be redirected to a connection that is not secure"
- Previous message: Eran Kampf: "Re: Security problem when dynamically creating directories"
- In reply to: howard_at_nospam.nospam: "Windows authentication and availability"
- Next in thread: howard_at_nospam.nospam: "Re: Windows authentication and availability"
- Reply: howard_at_nospam.nospam: "Re: Windows authentication and availability"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|