Policy
Set maximum Kerberos SSPI context token buffer size
Windows 11 25H2
Policy overview
Key metadata and intent for this policy.
Supported OS tags: Windows10, Windows10RT, Windows11, Windows7, Windows8, Windows81, WindowsRT, WindowsRT81, WindowsServer2003, WindowsServer2008, WindowsServer2012, WindowsServer2012R2, WindowsServer2016, WindowsVista, WindowsXP
This policy setting allows you to set the value returned to applications which request the maximum size of the SSPI context token buffer size. The size of the context token buffer determines the maximum size of SSPI context tokens an application expects and allocates. Depending upon authentication request processing and group memberships, the buffer might be smaller than the actual size of the SSPI context token. If you enable this policy setting, the Kerberos client or server uses the configured value, or the locally allowed maximum value, whichever is smaller. If you disable or do not configure this policy setting, the Kerberos client or server uses the locally configured value or the default value. Note: This policy setting configures the existing MaxTokenSize registry value in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters, which was added in Windows XP and Windows Server 2003, with a default value of 12,000 bytes. Beginning with Windows 8 the default is 48,000 bytes. Due to HTTP's base64 encoding of authentication context tokens, it is not advised to set this value more than 48,000 bytes.
Registry values
How enabled and disabled states update the registry.
| Registry location | Type | Enabled value | Disabled value |
|---|---|---|---|
| HKLM\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters\EnableMaxTokenSize | REG_DWORD | 1 | 0 |
Policy elements
Inputs and configuration options exposed by this policy.
| Element | Type | Registry mapping | Constraints & behavior |
|---|---|---|---|
Maximum size ID MaxTokenSize | decimal | HKLM\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters\MaxTokenSize Type REG_DWORD | Range: 12000 to 2147483647 |
Other policies in this category
Explore related policies at the same level.
- ComputerAllow retrieving the Azure AD Kerberos Ticket Granting Ticket during logonAt least Windows Server 2019, Windows 10 Version 2004
- ComputerAlways send compound authentication firstAt least Windows Server 2012 R2, Windows 8.1 or Windows RT 8.1
- ComputerConfigure hash algorithms for certificate logonAt least Windows 11 Version 22H2
- ComputerDefine host name-to-Kerberos realm mappingsAt least Windows Vista
- ComputerDefine interoperable Kerberos V5 realm settingsAt least Windows Vista
- ComputerDisable revocation checking for the SSL certificate of KDC proxy serversAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerEnable Delegated Managed Service Account logonsAt least Windows 11 Version 24H2
- ComputerFail authentication requests when Kerberos armoring is not availableAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerKerberos client support for claims, compound authentication and Kerberos armoringAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerRequire strict KDC validationAt least Windows Vista
- ComputerRequire strict target SPN match on remote procedure callsAt least Windows Server 2008 R2 or Windows 7
- ComputerSpecify KDC proxy servers for Kerberos clientsAt least Windows Server 2012, Windows 8 or Windows RT