With the server mode present on the IPA server, it should be able to fill the response from the extdom plugin with the shell and homedir easily.

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

description: Ticket was cloned from Red Hat Bugzilla (product ''Red Hat Enterprise Linux 6''): [https://bugzilla.redhat.com/show_bug.cgi?id=990688 Bug 990688]

{{{
1. Proposed title of this feature request
Allow per user modification to login shell and home directory by reading the
value from AD when there is a trusted relationship between AD and IPA.

1. Who is the customer behind the request?
   Account: name (acct #1168178)
   TAM customer: no
   SRM customer: no
   Strategic: no

2. What is the nature and description of the request?
   Currently there is only a default template applied by SSSD for the login shell
   and the home directory. SSSD should be able to read the unix home directory and
   shell attribute from AD and use that. If the value doesn't exist then it can
   use a default value.

3. Why does the customer need this? (List the business requirements here)
   He would like to customize home directories and login shells on a user by user
   basis.

4. How would the customer like to achieve this? (List the functional
   requirements here)

SSSD uses the unix login home directory and shell from AD.

The customer also suggested locally configuring an sssd value for each user.
This may be possible with something like the "username map" option used in the
smb.conf where another file is referenced that contains home directory and
shell values for users.

1. For each functional requirement listed, specify how Red Hat and the customer
   can test to confirm the requirement is successfully implemented.

The home directory and shell attributes listed in AD are used.

1. Is there already an existing RFE upstream or in Red Hat Bugzilla?
   A tracking bug was/is also going to be created in Red Hat Bugzilla by sbose
   He said to create this one for SSSD as well.

2. Does the customer have any specific timeline dependencies and which release
   would they like to target (i.e. RHEL5, RHEL6)?
   RHEL6

3. Is the sales team involved in this request and do they have any additional
   input?
   no

4. List any affected packages or components.
   sssd

5. Would the customer be able to assist in testing this functionality if
   implemented?
   Yes, this is a tech preview for IPA and they are currently evaluating it.
   }}} => Ticket was cloned from Red Hat Bugzilla (product ''Red Hat Enterprise Linux 6''): [https://bugzilla.redhat.com/show_bug.cgi?id=990688 Bug 990688]

{{{
1. Proposed title of this feature request
Allow per user modification to login shell and home directory by reading the
value from AD when there is a trusted relationship between AD and IPA.

1. What is the nature and description of the request?
   Currently there is only a default template applied by SSSD for the login shell
   and the home directory. SSSD should be able to read the unix home directory and
   shell attribute from AD and use that. If the value doesn't exist then it can
   use a default value.

2. Why does the customer need this? (List the business requirements here)
   He would like to customize home directories and login shells on a user by user
   basis.

3. How would the customer like to achieve this? (List the functional
   requirements here)

SSSD uses the unix login home directory and shell from AD.

The customer also suggested locally configuring an sssd value for each user.
This may be possible with something like the "username map" option used in the
smb.conf where another file is referenced that contains home directory and
shell values for users.

1. For each functional requirement listed, specify how Red Hat and the customer
   can test to confirm the requirement is successfully implemented.

The home directory and shell attributes listed in AD are used.

1. Is there already an existing RFE upstream or in Red Hat Bugzilla?
   A tracking bug was/is also going to be created in Red Hat Bugzilla by sbose
   He said to create this one for SSSD as well.

2. Does the customer have any specific timeline dependencies and which release
   would they like to target (i.e. RHEL5, RHEL6)?
   RHEL6

3. Is the sales team involved in this request and do they have any additional
   input?
   no

4. List any affected packages or components.
   sssd

5. Would the customer be able to assist in testing this functionality if
   implemented?
   Yes, this is a tech preview for IPA and they are currently evaluating it.
   }}}
   milestone: NEEDS_TRIAGE => SSSD 1.12 beta
   priority: major => minor
   summary: RFE: User's home directories and shells are not taken from AD when there is an IPA trust with AD => [RFE] User's home directories and shells are not taken from AD when there is an IPA trust with AD

The IPA dependency https://fedorahosted.org/freeipa/ticket/4031 is in NEEDS_TRIAGE, bumping this as well so we decide which milestone (corresponding to IPA's 4031) we want to work on this one.

milestone: SSSD 1.12 beta => NEEDS_TRIAGE

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12.1

Fields changed

design: => http://www.freeipa.org/page/V4/Extdom_plugin_enhancement_grouplist

Fields changed

changelog: => If the LDAP user entry of a user from a domain trusted by IPA has the login shell or the home directory defined those values are taken instead of auto-generated ones.

Mass-moving all tickets that didn't make 1.12.1 into 1.12.2

milestone: SSSD 1.12.1 => SSSD 1.12.2

Fields changed

owner: somebody => sbose
patch: 0 => 1
status: new => assigned

• master: 28c70f0

mark: => 0
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/3083

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.