Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product RHEL RFE): Bug 947196
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
Customer's LDAP directory has entries currently with %H listed for majority of
home directories. This %H macro is a feature of the Likewise product that
allows this value to be expanded differently for each OS. As they are wanting
sssd product to co-exists with likewise customer is wanting sssd to have
feature to also expand a macro to somehing defiened in the sssd.conf file.
Here is what Likewise product expands %H to by default:
# Default: Linux: /home
# Default: MacOS: /Users
# Default: SunOS: /export/home
design_review: => 0
review: True => 0
testsupdated: => 0
type: defect => enhancement
milestone: NEEDS_TRIAGE => SSSD 1.11 beta
priority: major => critical
rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=947196 947196] => [https://bugzilla.redhat.com/show_bug.cgi?id=947196 947196] todo
milestone: SSSD 1.12 beta => Interim Bucket
milestone: Interim Bucket => SSSD 1.12 beta
summary: RFE: Allow sssd to replace macro (ie. %H) with value specified in config file => [RFE] Allow sssd to replace macro (ie. %H) with value specified in config file
owner: somebody => lslebodn
patch: 0 => 1
status: new => assigned
Target release for private BZ947196 is "6.6"
Should we move this ticket from release "SSSD 1.12 beta"
to "SSSD 1.11.6"?
Yes, because we'll need to do a 1.11 backport at least for the DEBUG messages.
milestone: SSSD 1.12 beta => SSSD 1.11.6
resolution: => fixed
status: assigned => closed
rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=947196 947196] todo => [https://bugzilla.redhat.com/show_bug.cgi?id=947196 947196]
Metadata Update from @jhrozek:
- Issue assigned to lslebodn
- Issue set to the milestone: SSSD 1.11.6
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:
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.
to comment on this ticket.