Skip to content

Commit 093054b

Browse files
committed
do updates
1 parent 8710f6f commit 093054b

1 file changed

Lines changed: 11 additions & 15 deletions

File tree

  • src/pages/docs/security/authentication/active-directory

src/pages/docs/security/authentication/active-directory/index.md

Lines changed: 11 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: src/layouts/Default.astro
33
pubDate: 2023-01-01
4-
modDate: 2023-11-30
4+
modDate: 2026-03-05
55
title: Active Directory authentication
66
description: Octopus Deploy can use Windows credentials to identify users.
77
navOrder: 5
@@ -28,19 +28,19 @@ If you are using Active Directory Authentication with Octopus, there are two way
2828

2929
By default, Active Directory Authentication will use NTLM as the Authentication Scheme. In many circumstances, you can also configure Octopus to use Kerberos for authentication.
3030

31-
If you would like to use Kerberos for authentication, you should consider if you require User Mode authentication. User Mode is required for Kerberos authentication when Octopus is in a [High Availability](/docs/administration/high-availability) configuration. By default, Kerberos authentication for Octopus Deploy runs in Kernel Mode. The mode is dictated by the web server running Octopus Deploy, which can be configured using the `configure` command. Select HTTP.sys for Kernel Mode, or Kestrel for User Mode:
31+
If you would like to use Kerberos for authentication, you will need to use User Mode authentication (Kestrel). By default, Active Directory authentication for Octopus Deploy runs in Kernel Mode via HTTP.sys. The mode is dictated by the web server running Octopus Deploy, which can be configured using the `configure` command. Select HTTP.sys for Kernel Mode, or Kestrel for User Mode:
3232

3333
### Kernel Mode authentication via HTTP.sys (default) - Command Line
3434

35-
Select this mode if you require features of HTTP.sys, such as port sharing.
35+
Select this mode if you require features of HTTP.sys, such as port sharing. This mode supports NTLM in both single server and High Availability configurations.
3636

3737
```bash
3838
Octopus.Server.exe configure --webServer=HttpSys
3939
```
4040

4141
### User Mode authentication via Kestrel - Command Line
4242

43-
Select this mode for High Availability configurations.
43+
Select this mode if you require Kerberos authentication.
4444

4545
```bash
4646
Octopus.Server.exe configure --webServer=Kestrel
@@ -89,17 +89,13 @@ Without some additional configuration, AD authentication, whether forms-based or
8989

9090
### Supported setups for Active Directory authentication {#supported-active-directory-setups}
9191

92-
Octopus Deploy supports various options for Active Directory authentication.
92+
Octopus Deploy supports various options for Active Directory authentication. Both HTTP.sys and Kestrel web server modes are compatible with High Availability configurations. The choice of web server determines which authentication protocols are available.
9393

94-
:::div{.hint}
95-
Not all high availability and Active Directory configurations are supported. There are limitations on the use of Kerberos in high availability scenarios. This is due to a requirement to [use a machine level SPN in order to allow Kerberos to work](#configuring-kerberos) with our web server.
96-
:::
97-
98-
| Octopus Option | Single Octopus Server | High-Availability |
99-
|---------------------------------|-----------------------|-------------------|
100-
| NTLM | Yes | Yes |
101-
| Negotiate | Yes | No |
102-
| IntegratedWindowsAuthentication | Yes | No |
94+
| Octopus Option | HTTP.sys (Kernel Mode) | Kestrel (User Mode) |
95+
|---------------------------------|------------------------|----------------------|
96+
| NTLM | Yes | Yes |
97+
| Negotiate | NTLM only | Kerberos, NTLM |
98+
| IntegratedWindowsAuthentication | NTLM only | Kerberos, NTLM |
10399

104100
:::div{.hint}
105101
**Service Accounts and Kerberos**
@@ -139,7 +135,7 @@ setspn.exe -S HTTP/od.domain.local server1
139135
:::div{.hint}
140136
**HA Clusters**
141137

142-
If you are running a HA Octopus Deploy environment, Kerberos authentication is not currently supported. Please refer to our section on [Supported Setups for Active Directory Authentication](#supported-active-directory-setups)
138+
Kerberos authentication in a High Availability environment requires configuring Octopus to use Kestrel (User Mode). Please refer to our section on [Supported Setups for Active Directory Authentication](#supported-active-directory-setups).
143139
:::
144140

145141
For more information about configuration of SPNs [please see this microsoft support article](https://support.microsoft.com/en-us/help/929650/how-to-use-spns-when-you-configure-web-applications-that-are-hosted-on).

0 commit comments

Comments
 (0)