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.

Bug 1915471

Summary: Incomplete error message about insufficient access
Product: Red Hat Enterprise Linux 8 Reporter: Sergey Orlov <sorlov>
Component: ipaAssignee: Thomas Woerner <twoerner>
Status: CLOSED UPSTREAM QA Contact: ipa-qe <ipa-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.4CC: frenaud, pcech, rcritten, tscherf
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-19 13:24:30 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:
Embargoed:

Description Sergey Orlov 2021-01-12 17:23:54 UTC
Description of problem:
When a user does not have permission to perform actions on IPA server, the error message is incomplete

Version-Release number of selected component (if applicable):
ipa-server-4.9.0-1.module+el8.4.0+9274+259c83ee.x86_64

How reproducible:


Steps to Reproduce:
1. Set up IPA and establish Trust with an AD domain
2. kinit Administrator
3. ipa ping

Actual result: "ipa: ERROR: Insufficient access:  Invalid credentials"

Expected result "ipa: ERROR: Insufficient access: SASL(-14): authorization failure: Invalid credentials"

Additional info: 
Expected result is observed in Fedora32 [1] and in RHEL-8.3 (ipa-server-4.8.7-13)

Presence of two spaces after "Insufficient access:" makes me suspect that an empty string was used during template expansion.

[1] http://freeipa-org-pr-ci.s3-website.eu-central-1.amazonaws.com/jobs/1732f180-5480-11eb-8b52-fa163e35ece8/report.html

Comment 1 Florence Blanc-Renaud 2021-01-13 13:09:10 UTC
Please see the comments in https://pagure.io/freeipa/issue/8631. The new behavior is probably caused by commit cc0f692, fixing #4480 (Unexpected info returned to ldap request).

Comment 2 Sergey Orlov 2021-01-13 13:54:18 UTC
I checked that cc0f692 is included in 389-ds-base-1.4.3.16-6 in RHEL8.4 and not included in 389-ds-base-1.4.3.16-1.fc32 in Fedora 32, which correlates with different behavior on those two OSes 

As the issue is minor, I will update the upstream test.

Comment 3 Petr Čech 2021-01-19 13:24:30 UTC
It is implemented in upstream by https://pagure.io/freeipa/issue/8631, so it will go as part of rebase.

Comment 4 Florence Blanc-Renaud 2021-01-19 14:06:41 UTC
The test was fixed upstream:

master:
    4a3a39f ipatests: fix expected errmsg in TestTrust::test_ipa_commands_run_as_aduser