[jira] [Commented] (SYNCOPE-1467) RDN not allowed when an attribute of the group present also in the DN is changed
[ https://issues.apache.org/jira/browse/SYNCOPE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834737#comment-16834737 ] ASF subversion and git services commented on SYNCOPE-1467: -- Commit bb7c2ba5d2cb60abe7e8f4aeb48615e8c2e79647 in syncope's branch refs/heads/master from Marco Di Sabatino Di Diodoro [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=bb7c2ba ] [SYNCOPE-1467] Added test > 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)
[jira] [Commented] (SYNCOPE-1467) RDN not allowed when an attribute of the group present also in the DN is changed
[ https://issues.apache.org/jira/browse/SYNCOPE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834628#comment-16834628 ] ASF subversion and git services commented on SYNCOPE-1467: -- Commit 1ceecccec496e8d7e92042cb6dcd2e609e25f1d8 in syncope's branch refs/heads/2_1_X from Marco Di Sabatino Di Diodoro [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=1ceeccc ] [SYNCOPE-1467] Added test > 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)
[jira] [Commented] (SYNCOPE-1467) RDN not allowed when an attribute of the group present also in the DN is changed
[ https://issues.apache.org/jira/browse/SYNCOPE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834578#comment-16834578 ] ASF subversion and git services commented on SYNCOPE-1467: -- Commit 4baa5b56e5f199b71c248f4058b3841f25cef936 in syncope's branch refs/heads/2_0_X from Marco Di Sabatino Di Diodoro [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=4baa5b5 ] [SYNCOPE-1467] Added test > 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)
[jira] [Commented] (SYNCOPE-1467) RDN not allowed when an attribute of the group present also in the DN is changed
[ https://issues.apache.org/jira/browse/SYNCOPE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833625#comment-16833625 ] Marco Di Sabatino Di Diodoro commented on SYNCOPE-1467: --- The issue will be resolved on the ldap connector https://connid.atlassian.net/projects/LDAP/issues/LDAP-28 > 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 >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)