We are struggling to make Octopus authenticate our users via Active Directory (“Domain”), but without any success. Here’s the message from Windows audit log (please note that the box where Octopus sits is in DOMAIN1 whereas our users are in DOMAIN2, and there are trust relationships between the two):
An account failed to log on.
Security ID: SYSTEM
Account Name: ASPDEV01$
Account Domain: DOMAIN1
Logon ID: 0x3e7
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: DOMAIN2\user
Failure Reason: Unknown user name or bad password.
Sub Status: 0xc0000064
Caller Process ID: 0x10e0
Caller Process Name: D:\Octopus2\Server\Octopus.Server.exe
Workstation Name: ASPDEV01
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Octopus v1.6 on the very same machine in Windows authentication mode authorises our users absolutely fine. I understand that v1.6 runs under IIS whereas 2.0 uses some kind of embedded HTTP server and this is probably the cause of the problem. Maybe there’s a setting somewhere which will force Octopus to use DOMAIN2 instead of DOMAIN1 when authenticating?
Two instances run on the same box under Windows 2008R2 SP1 with that patch which is needed to install v2 applied.
Any ideas how to solve this?
Thank you very much