Re: Authentication of a user (single sign-on)
From: Dmitriy Lapshin [C# / .NET MVP] (x-code_at_no-spam-please.hotpop.com)
Date: 04/23/04
- Next message: Dmitriy Lapshin [C# / .NET MVP]: "Re: C# and destructors"
- Previous message: J Brad: "Socket.BeginReceive() Problem"
- In reply to: Peter Tragardh: "Re: Authentication of a user (single sign-on)"
- Next in thread: Peter Tragardh: "Re: Authentication of a user (single sign-on)"
- Reply: Peter Tragardh: "Re: Authentication of a user (single sign-on)"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 23 Apr 2004 16:37:55 +0300
> I gave MSS as an example of the workflow, not an example of the technical
> aspects. During my research I've learned that the term for the function
> I'm looking for is single sign-on, and that is how I see MSS. I never log
> on specifically to MSS, I only log on Windows, and if the users are
> correctly defined in MSS, I just "get in".
It's probably because the names of the VSS users match the Windows
logon names. AFAIK your logon name is the first thing the VSS client
attempts to log in to a VSS database, so if the two match, you
"just get in".
-- Dmitriy Lapshin [C# / .NET MVP] X-Unity Test Studio http://www.x-unity.net/teststudio.aspx Bring the power of unit testing to VS .NET IDE "Peter Tragardh" <peter.tragardh@hotmail.com> wrote in message news:Xns94D49403EBCCCpetertragardhhotmail@207.46.248.16... > I gave MSS as an example of the workflow, not an example of the technical > aspects. During my research I've learned that the term for the function > I'm looking for is single sign-on, and that is how I see MSS. I never log > on specifically to MSS, I only log on Windows, and if the users are > correctly defined in MSS, I just "get in". > > I can also imagine that my system has to have it's own user registry to > cope with it's internal permissions, what functions a user may or may not > use. If not, I'm curious of how such a solution might work. > > > "Dmitriy Lapshin [C# / .NET MVP]" <x-code@no-spam-please.hotpop.com> > wrote in news:#kGKksSKEHA.3728@TK2MSFTNGP12.phx.gbl: > > > Hello Peter, > > > > Not sure why do you've given SourceSafe as the example... SourceSafe > > databases maintain its own lists of users. > > Anyway, I think you should take a look at the WindowsIdentity and > > WindowsPrincipal classes: > > > > using System.Security.Principal; > > > > WindowsIdentity curUser = WindowsIdentity.GetCurrent(); > > bool allow = curUser.IsAuthenticated; > > > > WindowsPrincipal membership = new WindowsPrincipal(curUser); > > bool isAdmin = membership.IsInRole("BUILTIN\\Administrators"); > > > > >
- Next message: Dmitriy Lapshin [C# / .NET MVP]: "Re: C# and destructors"
- Previous message: J Brad: "Socket.BeginReceive() Problem"
- In reply to: Peter Tragardh: "Re: Authentication of a user (single sign-on)"
- Next in thread: Peter Tragardh: "Re: Authentication of a user (single sign-on)"
- Reply: Peter Tragardh: "Re: Authentication of a user (single sign-on)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|