Hi, I have a serious problem with the LDAP PUSH user update. When the matching rule is valid I want Syncope to update the user. It works with PULL but the PUSH returns 'error code 68 - Entry Already Exists' and server logs:
May 17 14:47:25 peta slapd[8476]: conn=3305380 op=9 SRCH attr=dc=rhino,dc=rediris,dc=es description uid May 17 14:47:25 peta slapd[8476]: conn=3305380 op=9 SEARCH RESULT tag=101 err=0 nentries=1 text= May 17 14:47:25 peta slapd[8476]: conn=3305380 op=10 MOD dn="[email protected],dc=rhino,dc=rediris,dc=es" May 17 14:47:25 peta slapd[8476]: conn=3305380 op=10 MOD attr=o sn eduPersonPrincipalName schacHomeOrganization eduPersonEntitlement mail uid cn displayName schacHomeOrganizationType description eduPersonAffiliation May 17 14:47:25 peta slapd[8476]: conn=3305380 op=10 RESULT tag=103 err=0 text= May 17 14:47:25 peta slapd[8476]: conn=3305380 op=11 *MODRDN* dn="[email protected],dc=rhino,dc=rediris,dc=es" May 17 14:47:25 peta slapd[8476]: conn=3305380 op=11 *RESULT tag=109 err=68* text= - Do a search (SRCH) - Update the user (MOD) - Update the RDN (MODRDN) and return error=68 This last step should'nt run. 1) Can I disable the execution of MODRDN in Syncope? 2) Why does Syncope try to update the user RDN? I attach my LDAP-Connector and LDAP-Resource configuration in json format, in addition to the complete error trace. Can somebody help me? Thanks! error-68-Syncope-connid.log <http://syncope-user.1051894.n5.nabble.com/file/t339127/error-68-Syncope-connid.log> LDAP-Resource.json <http://syncope-user.1051894.n5.nabble.com/file/t339127/LDAP-Resource.json> LDAP-Connector.json <http://syncope-user.1051894.n5.nabble.com/file/t339127/LDAP-Connector.json> -- Sent from: http://syncope-user.1051894.n5.nabble.com/
