Upgrade your Internet Experience
Microsoft.com
Welcome Sign in
.NET Framework Developer Center
Click to Rate and Give Feedback
MSDN
MSDN Library
.NET Development
.NET Framework 3.5
 AuthenticationTypes Enumeration
Collapse All/Expand All Collapse All
This page is specific to
Microsoft Visual Studio 2008/.NET Framework 3.5

Other versions are also available for the following:
.NET Framework Class Library
AuthenticationTypes Enumeration

The AuthenticationTypes enumeration specifies the types of authentication used in System.DirectoryServices. This enumeration has a FlagsAttribute attribute that allows a bitwise combination of its member values.

This enumeration has a FlagsAttribute attribute that allows a bitwise combination of its member values.

Namespace:  System.DirectoryServices
Assembly:  System.DirectoryServices (in System.DirectoryServices.dll)
 Syntax
Visual Basic (Declaration) 
<FlagsAttribute> _
Public Enumeration AuthenticationTypes
Visual Basic (Usage) 
Dim instance As AuthenticationTypes
C# 
[FlagsAttribute]
public enum AuthenticationTypes
Visual C++ 
[FlagsAttribute]
public enum class AuthenticationTypes
JScript 
public enum AuthenticationTypes
 Members
Member nameDescription
NoneEquates to zero, which means to use basic authentication (simple bind) in the LDAP provider.
SecureRequests secure authentication. When this flag is set, the WinNT provider uses NTLM to authenticate the client. Active Directory Domain Services uses Kerberos, and possibly NTLM, to authenticate the client. When the user name and password are a null reference (Nothing in Visual Basic), ADSI binds to the object using the security context of the calling thread, which is either the security context of the user account under which the application is running or of the client user account that the calling thread is impersonating.
EncryptionAttaches a cryptographic signature to the message that both identifies the sender and ensures that the message has not been modified in transit.
SecureSocketsLayerAttaches a cryptographic signature to the message that both identifies the sender and ensures that the message has not been modified in transit. Active Directory Domain Services requires the Certificate Server be installed to support Secure Sockets Layer (SSL) encryption.
ReadonlyServerFor a WinNT provider, ADSI tries to connect to a domain controller. For Active Directory Domain Services, this flag indicates that a writable server is not required for a serverless binding.
AnonymousNo authentication is performed.
FastBindSpecifies that ADSI will not attempt to query the Active Directory Domain Services objectClass property. Therefore, only the base interfaces that are supported by all ADSI objects will be exposed. Other interfaces that the object supports will not be available. A user can use this option to boost the performance in a series of object manipulations that involve only methods of the base interfaces. However, ADSI does not verify if any of the request objects actually exist on the server. For more information, see the topic "Fast Binding Option for Batch Write/Modify Operations" in the MSDN Library at http://msdn.microsoft.com/library. For more information about the objectClass property, see the "Object-Class" topic in the MSDN Library at http://msdn.microsoft.com/library.
SigningVerifies data integrity to ensure that the data received is the same as the data sent. The Secure flag must also be set to use signing.
SealingEncrypts data using Kerberos. The Secure flag must also be set to use sealing.
DelegationEnables Active Directory Services Interface (ADSI) to delegate the user's security context, which is necessary for moving objects across domains.
ServerBindIf your ADsPath includes a server name, specify this flag when using the LDAP provider. Do not use this flag for paths that include a domain name or for serverless paths. Specifying a server name without also specifying this flag results in unnecessary network traffic.
 Remarks

The Secure flag can be used in combination with other flags such as ReadonlyServer, FastBind.

Serverless binding refers to a process in which a client attempts to bind to an Active Directory Domain Services object without explicitly specifying an Active Directory Domain Services server in the binding string, for example:

LDAP://CN=jsmith,DC=fabrikam,DC=Com

This is possible because the Lightweight Directory Access Protocol (LDAP) provider relies on the locator services of Windows 2000 to find the best domain controller (DC) for the client. However, the client must have an account on the Active Directory Domain Services domain controller to take advantage of the serverless binding feature, and the domain controller that is used by a serverless bind will always be located in the default domain (the domain associated with the current security context of the thread that's doing the binding).

NoteNote:

None of these options are supported by the Novell Netware Directory Service (NDS) system provider.
 Platforms

Windows 7, Windows Vista, Windows XP SP2, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP Starter Edition, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows Server 2000 SP4, Windows Millennium Edition, Windows 98

The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.
 Version Information

.NET Framework

Supported in: 3.5, 3.0, 2.0, 1.1, 1.0
 See Also

Reference

System.DirectoryServices Namespace
DirectoryEntry
DirectorySearcher
SearchResult
System.DirectoryServices
Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
AuthenticationTypes Enum sample with PowerShell      Thomas Lee   |   Edit   |   Show History 
# enum-AuthenticationTypes.ps1
# Enum sample using PowerShell
# Thomas Lee - tfl@psp.co.uk
 
# Get enums
$enums=[enum]::GetValues([System.DirectoryServices.AuthenticationTypes]) 
# Display values
"System.DirectoryServices.AuthenticationTypes enum has {0} possible values:" -f $enums.count
$i=0
$enums | %{"Value {0}: {1}" -f $i,$_.tostring();$i++}
""
 
# Checking against an enum value 
$ToCheck = "Secure"
if ($ToCheck -eq  [System.DirectoryServices.AuthenticationTypes]::Secure) 
{"`$ToCheck is Secure"}
else 
{"`$ToCheck is NOT Secure"}

This script produces the following output:

PS C:\Documents and Settings\LeeT> 
D:\foo\enum-AuthenticationTypes.ps1
System.DirectoryServices.AuthenticationTypes enum has 11 possible values:
Value 0: None
Value 1: Secure
Value 2: SecureSocketsLayer
Value 3: SecureSocketsLayer
Value 4: ReadonlyServer
Value 5: Anonymous
Value 6: FastBind
Value 7: Signing
Value 8: Sealing
Value 9: Delegation
Value 10: ServerBind
 
$ToCheck is Secure

© 2010 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement
Page view tracker