Bug 1651334 - ipa group-add-member command failing with option --idoverrideusers
Summary: ipa group-add-member command failing with option --idoverrideusers
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: 8.0
Hardware: x86_64
OS: Linux
medium
unspecified
Target Milestone: rc
: 8.0
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-19 17:59 UTC by Varun Mylaraiah
Modified: 2023-07-31 22:37 UTC (History)
9 users (show)

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


Attachments (Terms of Use)
Error_dialog (59.87 KB, image/png)
2018-11-19 18:29 UTC, Varun Mylaraiah
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-7163 0 None None None 2021-10-25 18:11:34 UTC
Red Hat Issue Tracker RHELPLAN-38533 0 None None None 2021-10-25 18:11:33 UTC

Description Varun Mylaraiah 2018-11-19 17:59:18 UTC
Description of problem:
ipa group-add-member command failing with option --idoverrideusers

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

-Red Hat Enterprise Linux release 8.0 Beta (Ootpa)

-ipa-server-4.7.1-5.module+el8+2149+d62dbe01.x86_64
-ipa-idoverride-memberof-plugin-0.0.4-6.el8+2132+cbcb57bd.x86_64
-ipa-server-trust-ad-4.7.1-5.module+el8+2149+d62dbe01.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Setup ipa-server
2. Setup AD trust
3. Create ID override for AD user in the Default Trust View
4. Add AD user to admin group

Console output:
ipa-server-4.7.1-5.module+el8+2149+d62dbe01.x86_64
ipa-idoverride-memberof-plugin-0.0.4-6.el8+2132+cbcb57bd.x86_64
ipa-server-trust-ad-4.7.1-5.module+el8+2149+d62dbe01.x86_64
 
[root@vm-idm-014 ~]# ipa idoverrideuser-add 'default trust view' Administrator
-----------------------------------------------------
Added User ID override "Administrator"
-----------------------------------------------------
  Anchor to override: administrator


[root@vm-idm-014 ~]# ipa group-add-member admins --idoverrideusers=Administrator
Usage: ipa [global-options] group-add-member GROUP-NAME [options]
 
ipa: error: no such option: --idoverrideusers

Actual results:
ipa: error: no such option: --idoverrideusers

Expected results:
ipa group-add-membeer <GROUP-NAME> --idoverrideusers=<AD-USER@ADDOMAIN>
the command should add AD user into any system ipa group

Additional info:

Comment 1 Varun Mylaraiah 2018-11-19 18:12:36 UTC
--idoverrideusers option is missing in "ipa group-add-member --help"


Console output:
[root@vm-idm-014 ~]# ipa group-add-member --help
Usage: ipa [global-options] group-add-member GROUP-NAME [options]

Add members to a group.
Options:
  -h, --help      show this help message and exit
  --external=STR  Members of a trusted domain in DOM\name or name@domain form
  --all           Retrieve and print all attributes from the server. Affects
                  command output.
  --raw           Print entries as stored on the server. Only affects output
                  format.
  --no-members    Suppress processing of membership attributes.
  --users=STR     users to add
  --groups=STR    groups to add
  --services=STR  services to add
[root@vm-idm-014 ~]# 
[root@vm-idm-014 ~]#

Comment 2 Varun Mylaraiah 2018-11-19 18:27:32 UTC
In Webui showing "IPA Error 3007: RequirmentError" while adding members in "User ID overrides" tab

Steps to Reproduce in WebUI:
1. Go to Identity > ID View > click "Default Trust View"
2. Click "Add" button on the right-hand side
3. ADD <ADuser@addomain> in "user to override" field 
4. Hit "Add"
5. Go to Identity > Groups > click "admins"
6. Now Click "User ID overrides" tab (next to "External" tab)
7. Then click "Add" button.


Please refer the attached screenshot

Comment 3 Varun Mylaraiah 2018-11-19 18:29:21 UTC
Created attachment 1507315 [details]
Error_dialog

Comment 4 Rob Crittenden 2018-11-19 18:57:26 UTC
These are two separate issues.

For the CLI I'm inclined to close this as WONTFIX because this is not a supported option. If you want an RFE then make it so.

The second bug is unrelated to the first and there may be something going wrong there but it should be reported separately.

Comment 5 Varun Mylaraiah 2018-11-20 03:15:40 UTC
(In reply to Rob Crittenden from comment #4)
> These are two separate issues.
> 
> For the CLI I'm inclined to close this as WONTFIX because this is not a
> supported option. If you want an RFE then make it so.

This was working in the previous version of IPA
ipa-server-4.7.1-4.el8+2101+0c53917e.x86_64
ipa-idoverride-memberof-plugin-0.0.4-6.el8+2132+cbcb57bd.x86_64

> 
> The second bug is unrelated to the first and there may be something going
> wrong there but it should be reported separately.

Okay

Comment 7 Varun Mylaraiah 2018-11-20 11:30:55 UTC
reported separately Bugzilla for WebUI issue https://bugzilla.redhat.com/show_bug.cgi?id=1651577

Comment 8 Alexander Bokovoy 2018-11-26 14:41:11 UTC
I think this is not a bug at all. If you had run 'ipa' command before installing additional plugins for IPA, then your local ipa metadata cache will have a stale info.

Let's repurpose this bug to force metadata cache expiration in case a server fingerprint is different but the cache timeout is not there yet. Probably this is the real issue we need to fix instead.

Comment 14 joel 2019-10-22 17:35:53 UTC
Hello,

I have customer trying to follow instruction in our docs:

  CHAPTER 19. ENABLING AD USERS TO ADMINISTER IDM
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_identity_management/enabling-ad-user-to-administer-idm_certmonger-for-issuing-renewing-service-certs#idoverrides-to-allow-ad-user-to-administer-idm-fin

Is this a supported option? This is a year old from RCrit:

> For the CLI I'm inclined to close this as WONTFIX because this is not a supported option. If you want an RFE then make it so.

Comment 15 Rob Crittenden 2019-10-22 17:47:16 UTC
I was mistaken. It was a caching issue. The fix was: rm -rf ~/.cache/ipa/


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