Regression in Winbind: Cannot map SID->UID when using read-only idmap-backend "ad", rfc2307 uids

I am not sure I understand the issue fully, so please bear with me if I am missing something.

Since the ad idmap backend *is* read-only, isn't it to be expected that you cannot change the "mapping" ? Was it even possible in an earlier version of Samba?

I am also curious about what you are trying to achieve. Are you trying to override the uid handed out from the AD for a specific user on a specific machine?

s/map/resolve/

winbind 2:3.3.2-1ubuntu3 cannot resolve SID->UID. The mapping is there in the AD, automatically created by the user-add script. However, the new new version does not return UIDs any more. GIDs continue to work.

AD is and was alway readonly. To my knowledge Samba has only recently gained the feature of stacking idmapings, where you layer a writable idmap over the readonly AD-map to handle the case where Samba wants to create a new mapping. When Samba 3.3.2 failed to work as before, I consulted the documentation and found the suggestion that I should layer a writable idmap over the AD-map. I tried to do that, but without success. Samba still fails to resovle UIDs from AD, but instead of complaining it silently allocates a new (and wrong) mapping in the writable backend.

As far as I can remember (its been a couple of week since I found the issue), what works is:
name -> SID (wbinfo -n)
SID -> name (wbinfo -s)
SID -> GID (wbinfo -Y)
GID -> SID (wbinfo -G)

What does not work:
SID -> UID (wbinfo -S)
UID -> SID (wbinfo -U)
And yes, I used SIDs that do represent User-Objects and that have a UID-Attribute in AD.

The fact that GID conversion works but UID conversion fails makes it almost certainly an upstream regression in the 3.3-branch.
I couldn't find a Samba bug about this. Edgar, could you file a bug on the upstream bugzilla (bugzilla.samba.org) ? They will probably ask you for more logs/information so it's probably better if you do it directly.

I tried to reproduce the issue, and now GID-conversion curiously fails as well.

Anyway, created the upstream bug:
https://bugzilla.samba.org/show_bug.cgi?id=6322

Thanks Edgar !
https://bugzilla.samba.org/show_bug.cgi?id=6322#c5 hints that it is a known documentation and missing feature issue...

Thanks for the info.