We are having a problem with an application that reads the retrochangelog. We have a dual master environment and the issue is that the dns are change to lowercase on the replicated entry.
Will the 'return-exact-case' attribute fix that? Is there any replication setting I am missing?
A MOD on M1 would show ou=Users, o=MyDomain, in the access log
the replicated MOD in M2 access log will be ou=users,o=mydomain
Any ideas?
> We are having a problem with an application that
> reads the retrochangelog. We have a dual master
> environment and the issue is that the dns are change
> to lowercase on the replicated entry.
> Will the 'return-exact-case' attribute fix that?
No it won't
> Is
> there any replication setting I am missing?
No.
> A MOD on M1 would show ou=Users, o=MyDomain, in the
> access log
> the replicated MOD in M2 access log will be
> ou=users,o=mydomain
>
> Any ideas?
First of all, DNs are usually made of attributes that have a case insensitive syntax (ou, o, cn, uid...). Thus relying on the exact same representation of the values is not recommended, and not compliant with the LDAP specifications.
The DN logged in access log on the Replica is the normalized version (all lower case, insignificant spaces removed).
It is not possible to tune this behavior.
Regards,
Ludovic.
