Re: Client/Server application with single login-SecureStream?
- From: cmbardon@xxxxxxxxxxxxxxxxxxxx
- Date: 18 Jan 2006 04:41:10 -0800
If kerberos will only work with domain accounts, then would it be
possible to use NegotiateStream to authenticate a client on a server
that is NOT a member of a domain? You said that Kerberos will only
work on machines that belong to the same domain, or to domains that
trust each other, but I'm looking at a case where client A is a member
of domain D, and server B is connected to the same network as A, but is
not a member of any domains (just a windows server box configured on a
workgroup). Will B still be able to authenticate the client if it
opens a secureStream connection? In other words, if B is not a member
of the domain, can it still contact the domain controller to
authenticate?
.
- Follow-Ups:
- Re: Client/Server application with single login-SecureStream?
- From: Dominick Baier [DevelopMentor]
- Re: Client/Server application with single login-SecureStream?
- From: Joe Kaplan \(MVP - ADSI\)
- Re: Client/Server application with single login-SecureStream?
- References:
- Re: Client/Server application with single login-SecureStream?
- From: cmbardon
- Re: Client/Server application with single login-SecureStream?
- From: Dominick Baier [DevelopMentor]
- Re: Client/Server application with single login-SecureStream?
- Prev by Date: Re: System.Security.SecurityException: Request failed.
- Next by Date: Re: Securing a .NET webapp with ActiveDir and SQL-server?
- Previous by thread: Re: Client/Server application with single login-SecureStream?
- Next by thread: Re: Client/Server application with single login-SecureStream?
- Index(es):
Relevant Pages
|