Delen via


AuthenticationMechanisms Enumeration

When a request required authentication, but failed to authenticate, these are the different kinds of authentication mechanisms that the response can advertise back to the client. When multiple mechanisms are allowed for a URI, some may take precedence over others, and that order of precedence is not defined here. The obligation on the part of the authentication module is to be sure *not* to advertise themselves in the response when their mechanism is missing from the list.

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

Namespace:  Microsoft.TeamFoundation.Framework.Server
Assembly:  Microsoft.TeamFoundation.Framework.Server (in Microsoft.TeamFoundation.Framework.Server.dll)

Syntax

'Declaration
<FlagsAttribute> _
Public Enumeration AuthenticationMechanisms
[FlagsAttribute]
public enum AuthenticationMechanisms
[FlagsAttribute]
public enum class AuthenticationMechanisms
[<FlagsAttribute>]
type AuthenticationMechanisms
public enum AuthenticationMechanisms

Members

Member name Description
All The URI supports all valid authentication mechanisms.

Basic The response for this URI advertises that it supports basic authentication, if that module is configured.

Federated The response for this URI advertises that it supports federated authentication, if that module is configured.

FederatedRedirect The response for this URI advertises that it supports federated authentication by total hijack of the response and replacement with a 302, if that module is configured.

None The response for this URI does not advertise that it supports any authentication mechanisms.

OAuth The response for this URI advertises that it supports OAuth authentication, if that module is configured.

Windows The response for this URI advertises that it supports integrated Windows authentication, if that module is configured.

See Also

Reference

Microsoft.TeamFoundation.Framework.Server Namespace