Ive rebuilt OpenLDAP on provider to 2.4.31 but it's still happening. I've
rebuilt twice - first with SASL, then without and it makes no difference
either.
This is driving me crazy bannanas now. Anything in my config that's wrong?
What's the cause of Strong(er) authentication required
[Qian] Sorry, I am new to LDAP, can you please let me know how to
figure out which way I am using for DN format? By some ldap commands?
BTW, I installed and setup LDAP in a default way, so I guess the DN
format should be uid=ghenry,ou=Users,dc=example,dc=com because when
I login my machine
Remove your dn{} line.
Sorry, which dn line do you mean?
This?
authzTo: {0}dn:*
Yeah.
--
Kind Regards,
Gavin Henry.
Managing Director.
T +44 (0) 1224 279484
M +44 (0) 7930 323266
F +44 (0) 1224 824887
E ghe...@suretecsystems.com
Open Source. Open Solutions(tm).
No difference.
What were you hoping it would do?
I also tried to upgrade syncrepl to TLS and while replication works fine
over TLS, chaining still says Strong(er) authentication is needed.
And i get
50150d47 do_bind: dn () SASL mech EXTERNAL
50150d47 ==slap_sasl2dn: converting SASL name
cn=cn\3Dreplicator,o=webgate,st=some-state,c=au to a DN
I just discovered something odd.
I ran slapd -d 256 on the provider, then started the replicator, and then
did ldapmodify and look what i found:
50152ae5 conn=1020 op=0 BIND dn= method=128
50152ae5 conn=1020 op=0 RESULT tag=97 err=0 text=
50152ae5 conn=1020 op=1 MOD
Well looks like I figured it out. In the bottom of slapo-chain man page,
it says
All URIs not listed in the configuration are chained anonymously.
my chain-uri was ldap://ldap.provider.net:389/;
but my updateref was ldap://ldap.provider.net
After changing chain-uri to the same as updateref,
On 29 Jul 2012, at 11:08, elekktrett...@exemail.com.au
elekktrett...@exemail.com.au wrote:
No difference.
What were you hoping it would do?
Sorry, I replied in a rush!
Gavin.
Hello,
are special characters, especially German umlauts, acceptable in the
distinguished name?
I've accidentally discovered that CPAN's Net::LDAP::Entry module doesn't
support them (in the distinguished name). Other attributes are escaped
correctly.
Thank you in advance.
Chris
Hello,
are special characters, especially German umlauts, acceptable in the
distinguished name?
I've accidentally discovered that CPAN's Net::LDAP::Entry module doesn't
support them (in the distinguished name). Other attributes are escaped
correctly.
Hi Chris,
It depends on how you've
10 matches
Mail list logo
