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 1005267 - ldapwhoami does not works on s390x against Microsoft AD
Summary: ldapwhoami does not works on s390x against Microsoft AD
Keywords:
Status: CLOSED DUPLICATE of bug 1002625
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openldap
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-06 14:33 UTC by Patrik Kis
Modified: 2013-09-10 12:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-10 12:13:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Patrik Kis 2013-09-06 14:33:30 UTC 
Description of problem:
ldapwhoami -H ldap://sec-ad1.ad.baseos.qe -Y GSSAPI
fails on s390x

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

How reproducible:
100%

Steps to Reproduce:
1. Microsoft AD; not sure it it can be reproduced with openldap server too
2. 
# kinit Administrator.QE
Password for Administrator.QE: 
#  ldapwhoami -H ldap://sec-ad1.ad.baseos.qe -Y GSSAPI
ldap_sasl_interactive_bind_s: Unknown authentication method (-6)
	additional info: SASL(-4): no mechanism available: No worthy mechs found

Actual results:
error message

Expected results:
#  ldapwhoami -H ldap://sec-ad1.ad.baseos.qe -Y GSSAPI
SASL/GSSAPI authentication started
SASL username: Administrator.QE
SASL SSF: 56
SASL data security layer installed.
u:AD\Administrator
Comment 6 Jan Synacek 2013-09-10 12:13:38 UTC 
# cat /var/log/messages
...
Sep 10 12:10:31 ibm-z10-24 ldapwhoami: unable to dlopen /usr/lib64/sasl2/libgssapiv2.so: /usr/lib64/sasl2/libgssapiv2.so: undefined symbol: gsskrb5_register_acceptor_identity
Sep 10 12:10:31 ibm-z10-24 ldapwhoami: No worthy mechs found
...

Closing as dup of 1002625.

*** This bug has been marked as a duplicate of bug 1002625 ***
Note You need to log in before you can comment on or make changes to this bug.