Learn more about these different git repos.
Other Git URLs
Allow an option to specify a client-specific home directory, different from the default in the specified LDAP server.
for instance, something like:
ldap_override_home_directory /nfs/home/%user
(where /nfs/home/%user could be anything including an autofs mounted dir)
We already have the option to specify a different entry in LDAP via ldap_user_home_directory, but this would be a good option for a specialized client where we either don't have access to the home directory or we don't have the ability to modify the home directory entry and cannot rely on a consistent entry (such is my case).
Notes for implementation:
We will want to specify this option as
ldap_override_homedir_base = /nfs/home
There's no need to include the user substitution (I can't think of anything else we'd want to substitute besides the username, and that should always be last)
doc: 0 => 1 tests: 0 => 1
I was thinking about this some more this morning. We probably want this option to be available for all providers, not just LDAP.
What I was thinking we should do is store the original value in the LDB, but before returning the user information in the NSS responder, we should replace this value with the one matching the {{{override_homedir}}} option.
Additionally, it also occurred to me that we may want to have a variable substitution for the SSSD domain, so that it would be a simple matter to differentiate users with the same name in different domains.
And we should allow the username to be either just the username or the fully-qualified username.
So:
- %D: domain - %U: username - %F: fully-qualified username override_homedir = /home/%D/%U
or
override_homedir = /home/%F
This latter one would make sense for when {{{use_fully_qualified_names = TRUE}}}
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.4.0 priority: major => minor
milestone: SSSD 1.5.0 => SSSD 1.6.0
Related to #742
coverity: => owner: somebody => jhrozek upgrade: => 0
cc: => ktdreyer
patch: => 0 status: new => assigned
patch: 0 => 1
Master: d9d716b
resolution: => fixed status: assigned => closed
Backported to sssd-1-5
72c3252
milestone: SSSD 1.6.0 => SSSD 1.5.9 rhbz: =>
rhbz: => 0
Metadata Update from @euxneks: - Issue assigned to jhrozek - Issue set to the milestone: SSSD 1.5.9
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/1593
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.