DirectAccess use an HTTPS based Kerberos proxy for client authorization. Client authentication requests are sent to a Kerberos proxy service running on the DirectAccess server. The Kerberos proxy then sends Kerberos requests to Domain Controllers on behalf of the client.
This way, Windows Server 2012 R2 DirectAccess makes PKI deployment optional and simplifies configuration and management..
Base Class | Microsoft.Windows.ApplicationComponent |
Abstract | False |
Hosted | True |
Singleton | False |
Extension | False |
Accessibility | Public |
ElementId | db65bd80-ae45-1c33-ced6-558ac3e422f9 |
Property Name | Type | Display Name (ENU) | Description (ENU) | Key | Max Length | Min Length | Case Sensitive | Default Value | EnumType |
---|---|---|---|---|---|---|---|---|---|
System.Entity: | |||||||||
![]() |
string | Display Name | Display name of the object. | false | 4000 | 0 | False | ||
System.ConfigItem: | |||||||||
![]() |
enum | Object Status | Object status | false | 256 | 0 | System.ConfigItem.ObjectStatusEnum.Active | System.ConfigItem.ObjectStatusEnum | |
![]() |
enum | Asset Status | Asset status | false | 256 | 0 | System.ConfigItem.AssetStatusEnum | ||
![]() |
richtext | Notes | Notes | false | 4000 | 0 |
<ClassType ID="AP.Remote.Access.Class.Kerberos" Accessibility="Public" Abstract="false" Base="Windows!Microsoft.Windows.ApplicationComponent" Hosted="true" Singleton="false" Extension="false"/>