Bug 916195
| Summary: | Active Directory Test Domain failed | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Juanjo Marin <juanj.marin> |
| Component: | openldap | Assignee: | Jan Synacek <jsynacek> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | jsynacek, jv+fedora, rmeggins, stefw |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-03-04 10:21:36 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
Juanjo Marin
2013-02-27 14:12:56 UTC
Juanjo, please, can you try regular ldapsearch instead of ldapwhoami? Can you please tell the specific command you want me to try ? Yes, I can. Try this: ldapsearch -H ldap://DCA.CCUL.JUNTA-ANDALUCIA.ES -Y GSSAPI -b "" -s base + This is the output from this command: $ ldapsearch -H ldap://DCA.CCUL.JUNTA-ANDALUCIA.ES -Y GSSAPI -b "" -s base + SASL/GSSAPI authentication started SASL username: juanj.marin.JUNTA-ANDALUCIA.ES SASL SSF: 56 SASL data security layer installed. # extended LDIF # # LDAPv3 # base <> with scope baseObject # filter: (objectclass=*) # requesting: + # # dn: # search result search: 4 result: 0 Success # numResponses: 2 # numEntries: 1 Juanjo, shot in the dark: What happens when you add this to your krb5.conf file? [libdefaults] rdns = true Additionally what happens when you remove your krb5.conf file? 1) change file /etc/krb5.conf
[logging]
default = FILE:/var/log/krb5libs.log
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmind.log
[libdefaults]
rdns = true
dns_lookup_realm = false
ticket_lifetime = 24h
renew_lifetime = 7d
forwardable = true
# default_realm = EXAMPLE.COM
[realms]
# EXAMPLE.COM = {
# kdc = kerberos.example.com
# admin_server = kerberos.example.com
# }
[domain_realm]
# .example.com = EXAMPLE.COM
# example.com = EXAMPLE.COM
2) $ ldapwhoami -v -H ldap://DCA.CCUL.JUNTA-ANDALUCIA.ES -Y GSSAPI
ldap_initialize( ldap://DCA.CCUL.JUNTA-ANDALUCIA.ES:389/??base )
SASL/GSSAPI authentication started
SASL username: juanj.marin.JUNTA-ANDALUCIA.ES
SASL SSF: 56
SASL data security layer installed.
ldap_parse_result: Protocol error (2)
additional info: 0000203D: LdapErr: DSID-0C090C7D, comment: Unknown extended request OID, data 0, vece
Result: Protocol error (2)
Additional info: 0000203D: LdapErr: DSID-0C090C7D, comment: Unknown extended request OID, data 0, vece
3) $ ldapsearch -H ldap://DCA.CCUL.JUNTA-ANDALUCIA.ES -Y GSSAPI -b "" -s base +
SASL/GSSAPI authentication started
SASL username: juanj.marin.JUNTA-ANDALUCIA.ES
SASL SSF: 56
SASL data security layer installed.
# extended LDIF
#
# LDAPv3
# base <> with scope baseObject
# filter: (objectclass=*)
# requesting: +
#
#
dn:
# search result
search: 4
result: 0 Success
# numResponses: 2
# numEntries: 1
--------------------
1) $ sudo mv /etc/krb5.conf /etc/krb5.conf.bk
2) $ ldapwhoami -v -H ldap://DCA.CCUL.JUNTA-ANDALUCIA.ES -Y GSSAPI
ldap_initialize( ldap://DCA.CCUL.JUNTA-ANDALUCIA.ES:389/??base )
SASL/GSSAPI authentication started
SASL username: juanj.marin.JUNTA-ANDALUCIA.ES
SASL SSF: 56
SASL data security layer installed.
ldap_parse_result: Protocol error (2)
additional info: 0000203D: LdapErr: DSID-0C090C7D, comment: Unknown extended request OID, data 0, vece
Result: Protocol error (2)
Additional info: 0000203D: LdapErr: DSID-0C090C7D, comment: Unknown extended request OID, data 0, vece
3) $ ldapsearch -H ldap://DCA.CCUL.JUNTA-ANDALUCIA.ES -Y GSSAPI -b "" -s base +
SASL/GSSAPI authentication started
SASL username: juanj.marin.JUNTA-ANDALUCIA.ES
SASL SSF: 56
SASL data security layer installed.
# extended LDIF
#
# LDAPv3
# base <> with scope baseObject
# filter: (objectclass=*)
# requesting: +
#
#
dn:
# search result
search: 4
result: 0 Success
# numResponses: 2
# numEntries: 1
That's what I thought. As you can see, the authentication was successful. Your configuration on Linux side is correct. But your version of AD server doesn't support whoami extended operation, therefore you are receiving the error. Closing this report as NOTABUG. |