Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1383520
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
Description of problem: Regular expression used in sssd.conf not being able to consume an @-sign in the user/group name. How reproducible: Always Additional info: With Default re_expression : ----------------------------- [root@rhel7u1-2 ~]# getent group test@group [root@rhel7u1-2 ~]# getent group test@group [root@rhel7u1-2 ~]# chown -R pk:test@group /test1 chown: invalid group: ?pk:test@group? getent group test@group command does not return the group information until I execute id command. [root@rhel7u1-2 ~]# id pk uid=672401110(pk) gid=672400513(domain users) groups=672400513(domain users),672401124(test@group) [root@rhel7u1-2 ~]# getent group test@group test@group:*:672401124:pk With modified re_expression : ----------------------------- re_expression = ((?P<name>.+)@(?P<domain>[^@]+$)) use_fully_qualified_names = True [root@stcpbdnlv03p ~]# getent group secbuild-s@domain.com@otherdomain.com secbuild-s@domain.com@otherdomain.com:*:57266: [root@stcpbdnlv03p ~]# echo $? 0
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @jhrozek: - Custom field mark reset (from no) - Custom field patch reset (from 0) - Custom field review reset (from True) - Custom field sensitive reset (from 0) - Issue close_status updated to: None - Issue set to the milestone: SSSD 1.16.0 (was: SSSD Future releases (no date set yet))
Metadata Update from @jhrozek: - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Issue tagged with: RFE
Since we are required to release a new upstream tarball no later than Friday Oct-20, I'm moving tickets that will not be closed by that date to the next milestone, 1.16.1
Metadata Update from @jhrozek: - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1383520, https://bugzilla.redhat.com/show_bug.cgi?id=1509691 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1383520)
Issue linked to Bugzilla: Bug 1509691
Metadata Update from @jhrozek: - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Issue tagged with: postpone-to-2-0
Metadata Update from @jhrozek: - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Issue untagged with: postpone-to-2-0 - Issue set to the milestone: SSSD 2.0 (was: SSSD 1.16.1)
master: 4c79db6
Metadata Update from @fidencio: - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false)
I won't close this ticket for now as more work is planned on this area.
Metadata Update from @jhrozek: - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)
Metadata Update from @jhrozek: - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)
Metadata Update from @jhrozek: - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)
master
Metadata Update from @pbrezina: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
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/4252
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.