Hi all,
My Jira server just forgot all of it’s LDAP settings for no clear reason. While trying to
put the settings back, Jira is logging into 389ds by binding as the user
"cn=Atlassian,dc=x”.
389ds is in return responding as follows:
[LDAP: error code 48 - Anonymous access is not allowed]; nested exception is
javax.naming.AuthenticationNotSupportedException: [LDAP: error code 48 - Anonymous access
is not allowed]
[02/Nov/2018:17:11:23 +0200] conn=140630 op=0 BIND dn="cn=Atlassian,dc=x"
method=128 version=3
[02/Nov/2018:17:11:23 +0200] conn=140630 op=0 RESULT err=48 tag=97 nentries=0 etime=1
[02/Nov/2018:17:11:23 +0200] conn=140630 op=-1 fd=134 closed - B1
Why would 389ds complain that anonymous access is not allowed on a non-anonymous bind?
What am I missing?
(389-ds-base-1.2.11.15-97.el6_10.x86_64 on RHEL6)
Regards,
Graham
—