You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/pages/docs/security/authentication/active-directory/index.md
+11-15Lines changed: 11 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
layout: src/layouts/Default.astro
3
3
pubDate: 2023-01-01
4
-
modDate: 2023-11-30
4
+
modDate: 2026-03-05
5
5
title: Active Directory authentication
6
6
description: Octopus Deploy can use Windows credentials to identify users.
7
7
navOrder: 5
@@ -28,19 +28,19 @@ If you are using Active Directory Authentication with Octopus, there are two way
28
28
29
29
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.
30
30
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:
32
32
33
33
### Kernel Mode authentication via HTTP.sys (default) - Command Line
34
34
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.
36
36
37
37
```bash
38
38
Octopus.Server.exe configure --webServer=HttpSys
39
39
```
40
40
41
41
### User Mode authentication via Kestrel - Command Line
42
42
43
-
Select this mode for High Availability configurations.
43
+
Select this mode if you require Kerberos authentication.
44
44
45
45
```bash
46
46
Octopus.Server.exe configure --webServer=Kestrel
@@ -89,17 +89,13 @@ Without some additional configuration, AD authentication, whether forms-based or
89
89
90
90
### Supported setups for Active Directory authentication {#supported-active-directory-setups}
91
91
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.
93
93
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 |
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).
143
139
:::
144
140
145
141
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