On Чцв, 02 кас 2025, Bjarne Dein via FreeIPA-users wrote:
Thanks for all the great inputs here!

Now - I have got the sync between FreeIPA and Proxmox to work just great, 
except for one “tiny” detail - Group Description (aka described name of the 
group)

It was also a bit tricky with the Users real names, but found a good hint to 
make a couple of changes in `/etc/pve/domains.cfg` like:
Code:
sync_attributes email=mail,firstname=givenName,lastname=sn,comment=description
Whereas Users are now all good, I still only have the group id synced.

Does anyone have a fix for this?

What LDAP filter does proxmox use to retrieve this information?

If they'd include (objectclass=posixgroup) into the LDAP search terms,
they should get read rights to 'description' field. They also need to be
authenticated.

We have the following access control:

aci: (targetattr = "businesscategory || cn || createtimestamp || description |
 | entryusn || gidnumber || ipaexternalmember || ipantsecurityidentifier || ip
 auniqueid || membermanager || mepmanagedby || modifytimestamp || o || objectc
 lass || ou || owner || seealso")(targetfilter = "(|(objectclass=ipausergroup)
 (objectclass=posixgroup))")(version 3.0;acl "permission:System: Read Groups";
 allow (compare,read,search) userdn = "ldap:///anyone";;)

It means anyone authenticated to LDAP and asking for either
(objectclass=ipausergroup) or (objectclass=posixgroup) would be able to
read/compare/search any of the mentioned attributes.


--
/ Alexander Bokovoy
Sr. Principal Software Engineer
Security / Identity Management Engineering
Red Hat Limited, Finland

--
_______________________________________________
FreeIPA-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to