[ https://issues.apache.org/jira/browse/SYNCOPE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marco Di Sabatino Di Diodoro reassigned SYNCOPE-1467: ----------------------------------------------------- Assignee: Marco Di Sabatino Di Diodoro > RDN not allowed when an attribute of the group present also in the DN is > changed > -------------------------------------------------------------------------------- > > Key: SYNCOPE-1467 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1467 > Project: Syncope > Issue Type: Bug > Components: core > Affects Versions: 2.0.13, 2.1.4 > Reporter: Marco Di Sabatino Di Diodoro > Assignee: Marco Di Sabatino Di Diodoro > Priority: Major > Fix For: 2.0.14, 2.1.5, 3.0.0 > > > During rename of a group with LDAP resource assigned, Syncope returns an > exception > {code} > javax.naming.directory.SchemaViolationException: [LDAP: error code 67 - > NOT_ALLOWED_ON_RDN: failed for MessageType : MODIFY_REQUEST > Message ID : 66 > Modify Request > Object : 'cn=testLDAPGroup,ou=groups,o=isp' > Modification[0] > Operation : replace > Modification > owner: (null) Modification[1] > Operation : replace > Modification > description: (null) Modification[2] > Operation : replace > Modification > cn: > testLDAPGroup2org.apache.directory.api.ldap.model.message.ModifyRequestImpl@9aac12bb: > ERR_62 Entry cn=testLDAPGroup,ou=groups,o=isp does not have the cn > attributeType, which is part of the RDN";]; remaining name > 'cn=testLDAPGroup,ou=groups,o=isp' > Cause: [LDAP: error code 67 - NOT_ALLOWED_ON_RDN: failed for MessageType : > MODIFY_REQUEST > {code} > To replicate the issue with test data: > # pull from resource-ldap > # assign the group {{testLDAPGroup}} to {{resource-ldap}} > # rename {{testLDAPGroup}} to {{testLDAPGroup2}} > # propagation error > With a {{ldapmodify}} it's possible to rename the group > {code} > dn: cn=aGroupForPropagation,ou=Groups,o=isp > changetype: moddn > newrdn: cn=aGroupForPropagation1 > deleteoldrdn: 1 > newsuperior: ou=Groups,o=isp > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)