# OpcClassicAuthorizationService Enum

<span class="api-meta">since v2.32</span>

<dl class="api-definition">
<dt>Namespace</dt>
<dd><a href="../namespaces/opc.uafx.classic">Opc.UaFx.Classic</a></dd>
<dt>Assembly</dt>
<dd>Opc.UaFx.Advanced.dll</dd>
<dt>Package</dt>
<dd>Opc.UaFx.Advanced v2.59.0</dd>
</dl>

Defines what the server authorizes.

## Syntax

<div class="api-signature" data-lang="csharp">

```csharp
public enum OpcClassicAuthorizationService : long
```

</div>

<div class="api-signature" data-lang="vbnet">

```vbnet
Public Enum OpcClassicAuthorizationService As Long
```

</div>

## Inheritance

[Object](https://learn.microsoft.com/dotnet/api/system.object) → [ValueType](https://learn.microsoft.com/dotnet/api/system.valuetype) → [Enum](https://learn.microsoft.com/dotnet/api/system.enum) → **OpcClassicAuthorizationService**

## Fields

| Name | Value | Description |
|---|---|---|
| <a id="dce"></a>`Dce` | `2` | The server performs authorization checking using the client's DCE privilege attribute certificate (PAC) information, which is sent to the server with each remote procedure call made using the binding handle. Generally, access is checked against DCE access control lists (ACLs). |
| <a id="default"></a>`Default` | `4294967295` | DCOM can choose the authorization level using its normal security blanket negotiation algorithm. |
| <a id="name"></a>`Name` | `1` | The server performs authorization based on the client's principal name. |
| <a id="none"></a>`None` | `0` | The server performs no authorization. Currently, RPC\_C\_AUTHN\_WINNT, RPC\_C\_AUTHN\_GSS\_SCHANNEL, and RPC\_C\_AUTHN\_GSS\_KERBEROS all use only RPC\_C\_AUTHZ\_NONE. |

## Applies to

| Package | Versions |
|---|---|
| Opc.UaFx.Advanced | v2.32–v2.59 |