Zimbra v5.04, posix extension requires memberUid to contain a uidNumber. Why?

[davidh]

Hello,

I am just testing the upgrade to Zimbra 5.0.4 from 4.5.7 and have successfully got everything working, including the zimbra_posixaccount and zimbra_samba Zimlets.

However, the posix Zimlet appears to have been changed to require that the memberUid be the uidNumber rather than allowing the uid of the person to be used as previously. Why is this?

My understanding of the Posix LDAP schema is that you are meant to be using uid (i.e. username) in memberUid - certainly with pam_ldap and Radius, they seem to work well without using the specific number. Or have things changed since I set all this up last year?

I have patched the Zimlet to allow the prior functionality for the time being, but would be curious to know why the change was made...

Thanks!

Cheers,
David

[Greg]

My understanding of the Posix LDAP schema is that you are meant to be using uid (i.e. username) in memberUid - certainly with pam_ldap and Radius, they seem to work well without using the specific number. Or have things changed since I set all this up last year?

My mistake, I added the restriction. Please file a bug.

[davidh]

Greg,

Thanks for that - Bug #26423 has been raised.

Cheers,
David

[Flancer]

Seems like the bug has not been fixed since then. I have just migrated from Zimbra 4.5.5 to 5.0.6 and now one of my customers is stuck with the bug.

Wished it was mentioned in the release notes before the upgrade.

It would be even better if a fix can be found for this bug.

[phoenix]

It would be even better if a fix can be found for this bug.

There's a fix in the bug report, have you tried that? You should also vote on it.

[Flancer]

Yes, but would be good to have it released officially. Otherwise it might reappear after an upgrade.

[phoenix]

It will be released officially when the fix has been incorporated in the extensions. Vote on it and you'll be notified when it's fixed.