Learn more about these different git repos.
Other Git URLs
How to reproduce: configure sssd against AD the simplest is to test with python bindings
sh# python Python 2.7.5 (default, May 3 2017, 07:55:04) [GCC 4.8.5 20150623 (Red Hat 4.8.5-14)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import grp >>> import pysss_nss_idmap >>> >>> grp.getgrnam("Domain Users@sssdad2012r2.com") grp.struct_group(gr_name='sssdad2012r2.com\\domain users', gr_passwd='*', gr_gid=233600513, gr_mem=['sssdad2012r2.com\\testuser01-2012532']) >>> >>> dom_users = grp.getgrnam("Domain Users@sssdad2012r2.com") >>> >>> dom_users.gr_gid 233600513 >>> pysss_nss_idmap.getsidbyid(dom_users.gr_gid) {}
Additional info: Other functions from that module works quite well.
>>> pysss_nss_idmap.getsidbyname(dom_users.gr_name) {'sssdad2012r2.com\\domain users': {'type': 2, 'sid': u'S-1-5-21-179626712-3177568055-3763416661-513'}} >>> >>> pysss_nss_idmap.getnamebysid('S-1-5-21-179626712-3177568055-3763416661-513') {'S-1-5-21-179626712-3177568055-3763416661-513': {'type': 2, 'name': u'sssdad2012r2.com\\domain users'}
Metadata Update from @lslebodn: - Custom field version adjusted to 1.15.3 - Issue tagged with: regression
https://github.com/SSSD/sssd/pull/351
Metadata Update from @lslebodn: - Issue tagged with: PR
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.15.4
master:
Metadata Update from @lslebodn: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.16.0 (was: SSSD 1.15.4)
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/4511
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.