[29614] in Kerberos
Re: computer account change password with Windows 2008 domain
daemon@ATHENA.MIT.EDU (Russ Allbery)
Tue Apr 1 17:18:40 2008
To: "Tim Alsop" <Tim.Alsop@CyberSafe.Com>
In-Reply-To: <0D8F2EFD3A10E24DAEEA48EA6DA07D3048A5F5@postman-pat.csafe.local>
(Tim Alsop's message of "Tue\, 1 Apr 2008 14\:02\:18 +0100")
From: Russ Allbery <rra@stanford.edu>
Date: Tue, 01 Apr 2008 14:17:10 -0700
Message-ID: <87prt96zs9.fsf@windlord.stanford.edu>
MIME-Version: 1.0
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
"Tim Alsop" <Tim.Alsop@CyberSafe.Com> writes:
> We have discovered a problem when we try to set/change password for a
> computer account in AD on Windows Server 2008. The computer account is
> created so we can use it for a service/application, and the key is
> created from it's password (randomly generated) and extracted into a key
> table file.
>
> Our code is able to create the account (authenticating to AD using
> SASL/GSS/Kerberos) but when we try and set the computer account's
> password to a random value, the request is rejected, so it looks like AD
> on Windows 2008 has some changes which stop password changes for
> computer accounts, or maybe something which is stopping changes to
> passwords for accounts that use a principal name such as
> name/fqdn@REALM.
You don't say here *how* you're changing the password, but there are two
Active Directory bugs in Windows 2008 that you may be running into:
* Authentication to Active Directory using a principal that contains a
slash (such as service/foo) from a keytab generated by the Windows tool
is broken in Windows 2008. It works fine if there is no slash in the
principal. Microsoft has identified this as a bug and is working on a
fix.
* Microsoft broke password changes via the LDAP protocol with SASL GSSAPI
binds in Windows 2008. In Windows 2003, provided that you didn't try to
negotiate an SASL privacy layer, you could connect via TLS and
authenticate with GSSAPI and query or set the password attribute
directly. In Windows 2008, this no longer works; you always get the
error from the server that you are not permitted to negotiate a privacy
layer when using TLS, even though you're not trying to. We've already
filed this as a bug.
In both cases, if you have a support contract with Microsoft and this is a
problem that you're running into, please independently open your own bug;
the more customers they know this affects, the more likely we'll get a hot
fix.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
