Bug 1005267

Summary:	ldapwhoami does not works on s390x against Microsoft AD
Product:	Red Hat Enterprise Linux 7	Reporter:	Patrik Kis <pkis>
Component:	openldap	Assignee:	Jan Synacek <jsynacek>
Status:	CLOSED DUPLICATE	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	high
Version:	7.0	CC:	dspurek, jsynacek
Target Milestone:	rc	Keywords:	TestBlocker
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-10 12:13:38 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 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 ***