Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1687951 - ipa-client-automount needs option to specify domain
Summary: ipa-client-automount needs option to specify domain
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.6
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-12 18:16 UTC by joel
Modified: 2019-04-15 14:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description joel 2019-03-12 18:16:09 UTC
Description of problem:
ipa-client-automount automatically sets idmapping to the idm domain

Version-Release number of selected component (if applicable):
7.6

How reproducible:
constant

Steps to Reproduce:
1. run the command 
2.
3.

Actual results:
ipa-client-automount adds the Domain as last line in /etc/idmapd

Expected results:
option to specify the domain, so admins don't have to manually change mapping

Additional info:

Comment 2 Rob Crittenden 2019-03-13 13:26:31 UTC
Please provide a more detailed use case.

Comment 3 joel 2019-03-14 00:56:33 UTC
Cu is requesting an option for ipa-client-automount like "--domain"  so the "Domain =" directive within /etc/idmapd.conf is set from the command line. This is so admins don't have to manually change the domain from the default idm one to another.

Comment 4 Rob Crittenden 2019-03-14 12:04:55 UTC
Please confirm. The problem is that the client has a separate DNS domain than the IdM master so the Domain setting in /etc/idmapd.conf does not match the local value causing mapping to not work?

Comment 5 joel 2019-03-18 17:43:11 UTC
customer responded:

Actually, there are 3 domains we are dealing with...

Our DNS domain
Our IDM domain 
Our NFSv4 domain

All of these are different.  Therefore, ipa-client-automount should not change an existing domain in /etc/idmapd.conf.

Currently, ipa-client-automount changes whatever domain is configured in /etc/idmapd.conf to that of the IDM domain, breaking NFSv4 mapping


Note You need to log in before you can comment on or make changes to this bug.