freeipa.git/daemons, branch master

Fix uninitialized variable.

2011-03-24T19:20:03+00:00

https://fedorahosted.org/freeipa/ticket/1118

Make activated/inactivated groups optional

2011-03-01T16:02:55+00:00

directly change nsAccountLock on the entry if they are not used

Fixes: https://fedorahosted.org/freeipa/ticket/1021

Fix user synchronization.

2011-03-01T16:02:55+00:00

We need to set uidNumber and gidNumber to the magic values so that DNA can
assign appropriate Ids, otherwise the synchronization of users from AD will
fail with an error about posixAccount requiring a missing (uidNumber)
attribute.

Fixes: https://fedorahosted.org/freeipa/ticket/1020

Unbreak the ipa winsync plugin.

2011-03-01T16:02:55+00:00

Fix RDN construction.

Fixes: https://fedorahosted.org/freeipa/ticket/1015

Set the loginShell attribute on winsynced entries if configured

2011-03-01T16:02:55+00:00

Fixes: https://fedorahosted.org/freeipa/ticket/266

Reset target DN when generated UUID is used as RDN

2011-02-18T02:36:50+00:00

When the UUID plug-in generates a value that is used in the RDN
of the entry being added, the old DN is free'd and replaced with
the new DN.  The problem is that the operation in the pblock holds
a pointer to the old DN address.  This can cause other plug-ins to
reference garbage, leading to incorrect results or crashes.  This
was causing the attribute uniqueness plug-in to not work correctly,
resulting in duplicate netgroup entries.

The fix is to have the UUID plug-in reset the target DN after
changing the DN of the entry to be added.

ticket 963

Fix duplicate OIDs

2011-02-17T13:38:53+00:00

Apparently we forgot to check OID consistency between the schema and the
extensions, and we got duplicates.

Technically the schema was done later but it is easier to change the extensions
OIDs than to change the schema of current beta2/rc1 installations.

The only side effect is that older ipa-getkeytab and ipa-join binaries will
fail. So all the admin/client tools must be upgraded at the same time as well
as all the masters (otherwise some will show/accept the new OID while others
won't).

Fixes: https://fedorahosted.org/freeipa/ticket/976

Let 389-ds start up even if Kerboros is not configured yet.

2011-02-14T19:07:17+00:00

The situation is if during installation /etc/krb5.conf either doesn't
exist or configures no realms then 389-ds won't start up at all, causing
the installation to fail. This will let the server start up in a degraded
mode.

Also need to make the sub_dict in ldapupdate.py handle no realm otherwise
the installation will abort enabling the compat plugin.

ticket 606

Correctly report if this is a krb related password operation

2011-02-14T18:57:00+00:00

Fixes: https://fedorahosted.org/freeipa/ticket/949

Update krbExtraData too when changing passwords.

2011-02-14T18:36:27+00:00

Fixes: https://fedorahosted.org/freeipa/ticket/937