Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
From xdong's description in bug #869616:
2> Can use invalid SIDs - and message says member was added.(-1100 is invalid)
[root@xdong ~]# ipa group-add-member --external=s-1-5-21-2048782538-2375889789-2933420090-1100
Group name: bb
[member user]:
[member group]:
Group name: bb
Description: bb
External member: s-1-5-21-2048782538-2375889789-2933420090-1175, s-1-5-21-2048782538-2375889789-2933420090-1100
-------------------------
Number of members added 1
-------------------------
Also:
[root@rhel6-1 ~]# ipa group-add-member ad_group_external --external S-1-5-21-1246088475-3077293710-2580964704-1701
[member user]:
[member group]:
Group name: ad_group_external
Description: ad.example.com group external
External member: S-1-5-21-1246088475-3077293710-2580964704-1135,
S-1-5-21-1246088475-3077293710-2580964704-1136,
S-1-5-21-1246088475-3077293710-2580964704-1700,
S-1-5-21-1246088475-3077293710-2580964704-1701
Member users: admin
-------------------------
Number of members added 1
-------------------------
[root@rhel6-1 ~]# wbinfo -s S-1-5-21-1246088475-3077293710-2580964704-1701
failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND
Could not lookup sid S-1-5-21-1246088475-3077293710-2580964704-1701
Version-Release number of selected component (if applicable):
ipa-server-3.0.0-106.20121106T0229zgit881fc3a.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. Setup IPA Master with trust to AD domain
2. ipa group-add groupname --desc=desc
3. ipa group-add-member groupname --external <SID that does not exist in AD domain>
Actual results:
adds SID that can't be resolved from AD domain.
Expected results:
should reject or at least warn that this is the case?
Additional info:
This BZ turned into RFE to later add validation of the external users if they are entered by SIDs. Right now if the user is entered by SID there will be no attempt to validate the user. This would be documented.
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. The request was cloned to the upstream tracker long time ago (see link to the upstream ticket above), but it was unfortunately not given a priority neither in the upstream project, nor in Red Hat Enterprise Linux.
Given that this request is not planned for a close release, it is highly unlikely it will be fixed in this major version of Red Hat Enterprise Linux. We are therefore closing the request as WONTFIX.
To request that Red Hat reconsiders the decision, please reopen the Bugzilla with the help of Red Hat Customer Service and provide additional business and/or technical details about it's importance to you. Please note that you can still track this request or even offer help in the referred upstream Trac ticket to expedite the solution.