[389-users] Authentication method not supported

ilmir at atacom.kz ilmir at atacom.kz
Sat Jun 29 19:58:32 UTC 2013


Hello!
During the setup the Kolab on system with 389-ds I have found the 
following message: 
 
Your new DS instance 'xat' was successfully created.
Creating the configuration directory server . . .
Could not authenticate as user 
'uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot' to 
server 'ldap://xat.example.kz:389/o=NetscapeRoot'.  Error: Authentication 
method not supported

I thought that may be this is bug of kolab but new instance have the same 
problem.

[root at xat noarch]# ldapsearch -x -D "uid=kolab-service,ou=Special 
Users,dc=example,dc=kz"  -w secret -b "dc=example,dc=kz" -s sub 
"(objectclass=*)"
ldap_bind: Authentication method not supported (7)
        additional info: auth method not supported


[root at xat noarch]# ldapsearch -x -D "cn=directory manager"  -w secret -s 
base 
dn:
objectClass: top
namingContexts: dc=example,dc=kz
namingContexts: o=netscaperoot
defaultnamingcontext: dc=example,dc=kz
supportedExtension: 2.16.840.1.113730.3.5.7
supportedExtension: 2.16.840.1.113730.3.5.8
supportedExtension: 2.16.840.1.113730.3.5.3
supportedExtension: 2.16.840.1.113730.3.5.12
supportedExtension: 2.16.840.1.113730.3.5.5
supportedExtension: 2.16.840.1.113730.3.5.6
supportedExtension: 2.16.840.1.113730.3.5.9
supportedExtension: 2.16.840.1.113730.3.5.4
supportedExtension: 2.16.840.1.113730.3.6.5
supportedExtension: 2.16.840.1.113730.3.6.6
supportedExtension: 2.16.840.1.113730.3.6.7
supportedExtension: 2.16.840.1.113730.3.6.8
supportedExtension: 1.3.6.1.4.1.4203.1.11.1
supportedControl: 2.16.840.1.113730.3.4.2
supportedControl: 2.16.840.1.113730.3.4.3
supportedControl: 2.16.840.1.113730.3.4.4
supportedControl: 2.16.840.1.113730.3.4.5
supportedControl: 1.2.840.113556.1.4.473
supportedControl: 2.16.840.1.113730.3.4.9
supportedControl: 2.16.840.1.113730.3.4.16
supportedControl: 2.16.840.1.113730.3.4.15
supportedControl: 2.16.840.1.113730.3.4.17
supportedControl: 2.16.840.1.113730.3.4.19
supportedControl: 1.3.6.1.4.1.42.2.27.8.5.1
supportedControl: 1.3.6.1.4.1.42.2.27.9.5.2
supportedControl: 1.2.840.113556.1.4.319
supportedControl: 1.3.6.1.4.1.42.2.27.9.5.8
supportedControl: 1.3.6.1.4.1.4203.666.5.16
supportedControl: 2.16.840.1.113730.3.4.14
supportedControl: 2.16.840.1.113730.3.4.20
supportedControl: 1.3.6.1.4.1.1466.29539.12
supportedControl: 2.16.840.1.113730.3.4.12
supportedControl: 2.16.840.1.113730.3.4.18
supportedControl: 2.16.840.1.113730.3.4.13
supportedSASLMechanisms: EXTERNAL
supportedSASLMechanisms: GSSAPI
supportedSASLMechanisms: CRAM-MD5
supportedSASLMechanisms: PLAIN
supportedSASLMechanisms: DIGEST-MD5
supportedSASLMechanisms: LOGIN
supportedLDAPVersion: 2
supportedLDAPVersion: 3
vendorName: 389 Project
vendorVersion: 389-Directory/1.3.0.6 B2013.101.06
dataversion: 020130629192303020130629192303
netscapemdsuffix: cn=ldap://dc=xat,dc=example,dc=kz:389



I understand the this not the problem of credential and passwords. But it 
the problem of authentication mechanism of LDAP 
But where is core of this problem?

P.S: 389-ds is installed on Fedora 18 for PPC64 

Thank you!

--
Ilmir Mulyukov

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/389-users/attachments/20130630/a4ecb458/attachment.html>


More information about the 389-users mailing list