Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Donovan Follette

Donovan Follette donovanf

Niner since 2006

See more posts…

  • Designing Excel Solutions for the Web: Part 1

    @Tony Clews: Hi Tony, I have passed your request on to the C9 team. Please see my blog post here, http://bit.ly/k52dWk, and here, http://bit.ly/m6cGnG, for the Excel resources that I have just recently posted to MSDN in support of these two videos.

  • Demystified Series: WinForms App Single Sign On in 2 Lines of Code!

    neilhut:
    Thanks! The great thing about using the WindowsPrincipal and WindowsIdentity objects is that there is no set up required – yet these encapsulate information about Windows accounts whether the machine is domain attached or not. Therefore, simply pull in the appropriate namespace(s) and instantiate the objects required for either your single or repeated validation use. From there, if desired, the developer can interrogate the Name property to evaluate for a specific DOMAIN\ requirement for access to the application. The application could then be terminated with an error prompt based on the evaluation or possibly pop up another form to collect credentials for authentication to another identity store. Also, the Type property shows the type of authentication used to identify the user – Kerberos, NTLM, etc. There may be business reasons for the application to also make decisions based on this information.


    guercheLE:
    It appears that you need to adjust your syntax just a bit to:
    AppDomain.CurrentDomain.SetPrincipalPolicy(PrincipalPolicy.WindowsPrincipal)

    This should fix it. Smiley