Fields changed

blockedby: =>
blocking: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
review: True => 0
selected: =>
testsupdated: => 0
type: defect => enhancement

Fields changed

description: Ticket was cloned from Red Hat Bugzilla (product ''RHEL RFE''): [https://bugzilla.redhat.com/show_bug.cgi?id=947224 Bug 947224]

''Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.''

As for replacing spaces in group names, this is something I'm
interested to make it easier to do a drop in replacement for Likewise.

My group has many things (scripts, sudo config files, etc.) that are
testing for matches of the group name presented by Likewise. ("ldap
group" would be "ldap^group"). Who knows what all the developers
have set up with "carrot names", so if we convert a box from
Likewise to use SSSD without emulating the current behavior, we
won't be able to predict all the things that will break.

Customer would like to be able to replace a space with a '^' character;
however, think best functionality would be to have this character defined a
configuration file. => Ticket was cloned from Red Hat Bugzilla (product ''RHEL RFE''): [https://bugzilla.redhat.com/show_bug.cgi?id=947224 Bug 947224]

''Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.''

As for replacing spaces in group names, this is something I'm
interested to make it easier to do a drop in replacement for Likewise.

My group has many things (scripts, sudo config files, etc.) that are
testing for matches of the group name presented by Likewise. ("ldap
group" would be "ldap{{{^}}}group"). Who knows what all the developers
have set up with "carrot names", so if we convert a box from
Likewise to use SSSD without emulating the current behavior, we
won't be able to predict all the things that will break.

Customer would like to be able to replace a space with a '{{{^}}}' character;
however, think best functionality would be to have this character defined a
configuration file.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11 beta
rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=947224 947224] => [https://bugzilla.redhat.com/show_bug.cgi?id=947224 947224] todo

Fields changed

changelog: =>
milestone: SSSD 1.12 beta => Interim Bucket
priority: major => critical

Fields changed

milestone: Interim Bucket => SSSD 1.12 beta

Fields changed

summary: RFE: Add option for sssd to replace space with specified character in LDAP group => [RFE] Add option for sssd to replace space with specified character in LDAP group

Fields changed

owner: somebody => lslebodn

Fields changed

milestone: SSSD 1.12 beta => SSSD 1.11.6

This feature is requested by downstream.

Lukas is working on a patch, but it won't be ready in time for the 1.11.6 release. I'm moving the ticket out to 1.11.7, downstream will be patches atop 1.11.6

milestone: SSSD 1.11.6 => SSSD 1.11.7

Fields changed

rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=947224 947224] todo => [https://bugzilla.redhat.com/show_bug.cgi?id=947224 947224]

Fields changed

patch: 0 => 1
status: new => assigned

• master:
  • 21bc143c2855638242e9dfe01ea66198b5883b8a
  • 022c6b90bb37851c0e8704c0e5388ebc113c6470
  • 462db32918a05097652f8232cd6c8d78a826e63c
• sssd-1-11:
  • c2859eec9d110d0062dbc5733fa842fd99d1edeb
  • 50d24652b5321f4cc5709bc0877dde5da4e67f08
  • 31cd021079212a78ebeb6ec2f10d66acc160f89b

_comment0: * master:
21bc143c2855638242e9dfe01ea66198b5883b8a
022c6b90bb37851c0e8704c0e5388ebc113c6470
462db32918a05097652f8232cd6c8d78a826e63c
* sssd-1-11:
c2859eec9d110d0062dbc5733fa842fd99d1edeb
50d24652b5321f4cc5709bc0877dde5da4e67f08
31cd021079212a78ebeb6ec2f10d66acc160f89b
=> 1406536548892433
resolution: => fixed
status: assigned => closed

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/2896

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.