Bug 1123453

Summary: [RFE] ipactl does not inlude whether or not nis and compat functions are enabled
Product: Red Hat Enterprise Linux 7 Reporter: Xiyang Dong <xdong>
Component: ipaAssignee: Martin Kosek <mkosek>
Status: CLOSED NOTABUG QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: rcritten
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-28 07:33:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Xiyang Dong 2014-07-25 17:33:59 UTC
Description of problem:

NIS functionality is not enabled on ipa server by default

should we include nis and compat functions in ipactl status?

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


How reproducible:

Always

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 2 Rob Crittenden 2014-07-25 18:07:52 UTC
I don't think so. These aren't exactly running services.

Both are 389-ds plugins.

ipa-compat-manage status can be used to determine whether the plugin is enabled or not.

ipa-nis-manage has no status option. I can see how adding that might be nice.

It might also be nice to use autobind if these are executed as root (with some handling around in case the ldapi socket doesn't exist).

Comment 3 Martin Kosek 2014-07-28 07:33:52 UTC
(In reply to Xiyang Dong from comment #0)
> Description of problem:
> 
> NIS functionality is not enabled on ipa server by default
> 
> should we include nis and compat functions in ipactl status?

Rob is correct, NIS is a 389-ds-base plugin. As NIS is deprecating (ed) mean for IdM, it should not be enabled by default, but rather only when needed. For example, when NIS is being migrated:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/migrating-from-nis.html


(In reply to Rob Crittenden from comment #2)
...
> ipa-nis-manage has no status option. I can see how adding that might be nice.

Rob, please feel free to file an upstream RFE, I do not think it needs to be linked to this Bugzilla.

> It might also be nice to use autobind if these are executed as root (with
> some handling around in case the ldapi socket doesn't exist).

We have ticket #2957 to make that happen. I widened it's scope to also cover ipa-nis-manage and ipa-compat-manage:
https://fedorahosted.org/freeipa/ticket/2957

This is now in rather late release, if either of you consider that a priority, please tell me.

In any case, I think all points of this Bugzilla are now covered, closing as NOTABUG. Please re-open if you strongly disagree and we will discuss.