Re: Want to contribute
Hi, As per the provided guideline, I need to submit the signed CLA. To whom I need to send those documents? Regards, Atul R. More. Cell: +91 9970157167 On Thu, May 2, 2019 at 10:44 PM Atul More wrote: > Hi, > > Sure, I will start look into it. > > Regards, > Atul R. More. > Cell: +91 9970157167 > > > On Thu, May 2, 2019 at 3:32 PM Francesco Chicchiriccò > wrote: > >> On 01/05/19 17:52, Atul More wrote: >> > Hi, >> > >> > I am interested to work on Syncope project especially on development >> side. >> > I have total 13+ years of experience in Java/Spring and related >> > technologies. Also experience with IAM/GRC domain(basic). >> > >> > Just want to understand, how can I do that? >> > From where to start? >> Hi Atul, >> welcome to Apache Syncope! >> >> I'd suggest you take first a look at [1] and to submit your ICLA, since >> you intend to contribute. >> >> Then, you can get yourself acquainted with using Syncope [2][3], the >> build process [4] and finally start looking at issues on JIRA [5]. >> >> Some ideas for first-time contributions can be: >> >> * SYNCOPE-1332 - to review the whole code on master branch in order to >> see if there are language features from Java 11 we are not currently >> using >> * SYNCOPE-1403 - to enhance the Netbeans IDE plugin in order to use >> the actual classpath when building Groovy classes >> * SYNCOPE-1218 - to enhance the Admin Console with capability to >> persist the Topology layout across sessions (and users, possibly) >> * SYNCOPE-1465 - to augment the information stored about Task and >> Report execution >> * SYNCOPE-1466 - to augment the metadata stored about Users, Groups >> and Any Objects >> >> Feel free to ask, should you need any guidance. >> Regards. >> >> [1] http://syncope.apache.org/contributing >> [2] http://syncope.apache.org/docs/getting-started.html >> [3] http://syncope.apache.org/docs/reference-guide.html >> [4] http://syncope.apache.org/building >> [5] https://issues.apache.org/jira/projects/SYNCOPE/issues/ >> >> -- >> Francesco Chicchiriccò >> >> Tirasa - Open Source Excellence >> http://www.tirasa.net/ >> >> Member at The Apache Software Foundation >> Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail >> http://home.apache.org/~ilgrosso/ >> >>
[jira] [Assigned] (SYNCOPE-1460) Keymaster for dynamic Domain management
[ https://issues.apache.org/jira/browse/SYNCOPE-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-1460: --- Assignee: Francesco Chicchiriccò > Keymaster for dynamic Domain management > --- > > Key: SYNCOPE-1460 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1460 > Project: Syncope > Issue Type: Sub-task > Components: keymaster >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1459) Keymaster for Service Discovery
[ https://issues.apache.org/jira/browse/SYNCOPE-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834784#comment-16834784 ] ASF subversion and git services commented on SYNCOPE-1459: -- Commit 9b115109b940470e6f1c183e0bd602b9d73ed9d1 in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=9b11510 ] [SYNCOPE-1459] Adding console view > Keymaster for Service Discovery > --- > > Key: SYNCOPE-1459 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1459 > Project: Syncope > Issue Type: Sub-task > Components: keymaster >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1459) Keymaster for Service Discovery
[ https://issues.apache.org/jira/browse/SYNCOPE-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1459. - Resolution: Fixed > Keymaster for Service Discovery > --- > > Key: SYNCOPE-1459 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1459 > Project: Syncope > Issue Type: Sub-task > Components: keymaster >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (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:all-tabpanel
]
Marco Di Sabatino Di Diodoro resolved SYNCOPE-1467.
---
Resolution: Fixed
> 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=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-1421) New Enduser UI
[ https://issues.apache.org/jira/browse/SYNCOPE-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834665#comment-16834665 ] ASF subversion and git services commented on SYNCOPE-1421: -- Commit cf294a26b3ed348d10055de8edca322ccdbf4770 in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=cf294a2 ] [SYNCOPE-1421] Domain management - missing updates > New Enduser UI > -- > > Key: SYNCOPE-1421 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1421 > Project: Syncope > Issue Type: Sub-task > Components: enduser >Reporter: Francesco Chicchiriccò >Assignee: Andrea Patricelli >Priority: Major > Fix For: 3.0.0 > > > Create new Enduser UI with same features as current, but fully built on the > same grounds as Admin Console, to maximize reuse. > Sub tasks: > * -Customize shape: define CSS and restore- > * -Add captcha- > * -Merge common static resources into UI Commons module- > * -Fix hotswap profile- > * -Password reset page- > * -Confirm password reset page- > * User request management > * Customizability through JSON file > * -Must change password page- > * -i18n management- > * -Landing page- (deprecated) > * Extensions management > * Old enduser code removal > * -Domain management (clean also properties files, Docker images, etc.)- > * Automated tests with WicketTester -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1421) New Enduser UI
[ https://issues.apache.org/jira/browse/SYNCOPE-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834634#comment-16834634 ] ASF subversion and git services commented on SYNCOPE-1421: -- Commit 7cd8ab0920be0f891f9b2625dd2890c069aefff7 in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=7cd8ab0 ] [SYNCOPE-1421] Domain management > New Enduser UI > -- > > Key: SYNCOPE-1421 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1421 > Project: Syncope > Issue Type: Sub-task > Components: enduser >Reporter: Francesco Chicchiriccò >Assignee: Andrea Patricelli >Priority: Major > Fix For: 3.0.0 > > > Create new Enduser UI with same features as current, but fully built on the > same grounds as Admin Console, to maximize reuse. > Sub tasks: > * -Customize shape: define CSS and restore- > * -Add captcha- > * -Merge common static resources into UI Commons module- > * -Fix hotswap profile- > * -Password reset page- > * -Confirm password reset page- > * User request management > * Customizability through JSON file > * -Must change password page- > * -i18n management- > * -Landing page- (deprecated) > * Extensions management > * Old enduser code removal > * Domain management (clean also properties files, Docker images, etc.) > * Automated tests with WicketTester -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SYNCOPE-1421) New Enduser UI
[ https://issues.apache.org/jira/browse/SYNCOPE-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1421: Description: Create new Enduser UI with same features as current, but fully built on the same grounds as Admin Console, to maximize reuse. Sub tasks: * -Customize shape: define CSS and restore- * -Add captcha- * -Merge common static resources into UI Commons module- * -Fix hotswap profile- * -Password reset page- * -Confirm password reset page- * User request management * Customizability through JSON file * -Must change password page- * -i18n management- * -Landing page- (deprecated) * Extensions management * Old enduser code removal * -Domain management (clean also properties files, Docker images, etc.)- * Automated tests with WicketTester was: Create new Enduser UI with same features as current, but fully built on the same grounds as Admin Console, to maximize reuse. Sub tasks: * -Customize shape: define CSS and restore- * -Add captcha- * -Merge common static resources into UI Commons module- * -Fix hotswap profile- * -Password reset page- * -Confirm password reset page- * User request management * Customizability through JSON file * -Must change password page- * -i18n management- * -Landing page- (deprecated) * Extensions management * Old enduser code removal * Domain management (clean also properties files, Docker images, etc.) * Automated tests with WicketTester > New Enduser UI > -- > > Key: SYNCOPE-1421 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1421 > Project: Syncope > Issue Type: Sub-task > Components: enduser >Reporter: Francesco Chicchiriccò >Assignee: Andrea Patricelli >Priority: Major > Fix For: 3.0.0 > > > Create new Enduser UI with same features as current, but fully built on the > same grounds as Admin Console, to maximize reuse. > Sub tasks: > * -Customize shape: define CSS and restore- > * -Add captcha- > * -Merge common static resources into UI Commons module- > * -Fix hotswap profile- > * -Password reset page- > * -Confirm password reset page- > * User request management > * Customizability through JSON file > * -Must change password page- > * -i18n management- > * -Landing page- (deprecated) > * Extensions management > * Old enduser code removal > * -Domain management (clean also properties files, Docker images, etc.)- > * Automated tests with WicketTester -- 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-1459) Keymaster for Service Discovery
[ https://issues.apache.org/jira/browse/SYNCOPE-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834466#comment-16834466 ] ASF subversion and git services commented on SYNCOPE-1459: -- Commit 1940edb89c1e4a839f6bd2c2e82c690aae8ab3b5 in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=1940edb ] [SYNCOPE-1459] Service Discovery enabled among Core / Console / Enduser > Keymaster for Service Discovery > --- > > Key: SYNCOPE-1459 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1459 > Project: Syncope > Issue Type: Sub-task > Components: keymaster >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1470) Flowable extension not working with MariaDB
[
https://issues.apache.org/jira/browse/SYNCOPE-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834449#comment-16834449
]
ASF subversion and git services commented on SYNCOPE-1470:
--
Commit 3419d9eddfe0bf74e3a8b108f43242b6aa654e19 in syncope's branch
refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=3419d9e ]
[SYNCOPE-1470] Workaround (as Flowable does not support MariaDB): treat MariaDB
as MySQL
> Flowable extension not working with MariaDB
> ---
>
> Key: SYNCOPE-1470
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1470
> Project: Syncope
> Issue Type: Bug
> Components: extensions
>Affects Versions: 2.1.4
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.1.5, 3.0.0
>
>
> When enabling the Flowable extension and using MariaDB for internal storage,
> the following exception is raised during Core startup:
> {code}
> org.flowable.common.engine.api.FlowableException: couldn't deduct database
> type from database product name 'MariaDB'
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1470) Flowable extension not working with MariaDB
[
https://issues.apache.org/jira/browse/SYNCOPE-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-1470.
-
Resolution: Fixed
> Flowable extension not working with MariaDB
> ---
>
> Key: SYNCOPE-1470
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1470
> Project: Syncope
> Issue Type: Bug
> Components: extensions
>Affects Versions: 2.1.4
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.1.5, 3.0.0
>
>
> When enabling the Flowable extension and using MariaDB for internal storage,
> the following exception is raised during Core startup:
> {code}
> org.flowable.common.engine.api.FlowableException: couldn't deduct database
> type from database product name 'MariaDB'
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1470) Flowable extension not working with MariaDB
[
https://issues.apache.org/jira/browse/SYNCOPE-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834447#comment-16834447
]
ASF subversion and git services commented on SYNCOPE-1470:
--
Commit cfd9c02ba39e11c10d8294ca249997f6bf672987 in syncope's branch
refs/heads/2_1_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=cfd9c02 ]
[SYNCOPE-1470] Workaround (as Flowable does not support MariaDB): treat MariaDB
as MySQL
> Flowable extension not working with MariaDB
> ---
>
> Key: SYNCOPE-1470
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1470
> Project: Syncope
> Issue Type: Bug
> Components: extensions
>Affects Versions: 2.1.4
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.1.5, 3.0.0
>
>
> When enabling the Flowable extension and using MariaDB for internal storage,
> the following exception is raised during Core startup:
> {code}
> org.flowable.common.engine.api.FlowableException: couldn't deduct database
> type from database product name 'MariaDB'
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SYNCOPE-1470) Flowable extension not working with MariaDB
Francesco Chicchiriccò created SYNCOPE-1470:
---
Summary: Flowable extension not working with MariaDB
Key: SYNCOPE-1470
URL: https://issues.apache.org/jira/browse/SYNCOPE-1470
Project: Syncope
Issue Type: Bug
Components: extensions
Affects Versions: 2.1.4
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
Fix For: 2.1.5, 3.0.0
When enabling the Flowable extension and using MariaDB for internal storage,
the following exception is raised during Core startup:
{code}
org.flowable.common.engine.api.FlowableException: couldn't deduct database type
from database product name 'MariaDB'
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (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:all-tabpanel
]
Marco Di Sabatino Di Diodoro reopened SYNCOPE-1467:
---
> 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] [Resolved] (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:all-tabpanel
]
Marco Di Sabatino Di Diodoro resolved SYNCOPE-1467.
---
Resolution: Fixed
> 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] [Assigned] (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: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)
[jira] [Commented] (SYNCOPE-1469) MySQL with JSON support: errors during startup
[
https://issues.apache.org/jira/browse/SYNCOPE-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834430#comment-16834430
]
ASF subversion and git services commented on SYNCOPE-1469:
--
Commit 0e65daf4038e9830a9a7efe3803a697c40be8d52 in syncope's branch
refs/heads/2_1_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=0e65daf ]
[SYNCOPE-1469] Fixing Docker too
> MySQL with JSON support: errors during startup
> --
>
> Key: SYNCOPE-1469
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1469
> Project: Syncope
> Issue Type: Bug
> Components: core, docker
>Affects Versions: 2.1.4
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Labels: json, mysql
> Fix For: 2.1.5, 3.0.0
>
>
> There are some errors in the predefined configuration, which prevent normal
> Core startup, as some classes ({{Conf, CPlainAttr, CPlainAttrValue,
> CPlainAttrUniqueValue}}) are not defined when MySQL with JSON support is
> enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1469) MySQL with JSON support: errors during startup
[
https://issues.apache.org/jira/browse/SYNCOPE-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834429#comment-16834429
]
ASF subversion and git services commented on SYNCOPE-1469:
--
Commit 4cf2d5c306e1a89350294821924365fe587be16c in syncope's branch
refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=4cf2d5c ]
[SYNCOPE-1469] Fixing Docker too
> MySQL with JSON support: errors during startup
> --
>
> Key: SYNCOPE-1469
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1469
> Project: Syncope
> Issue Type: Bug
> Components: core, docker
>Affects Versions: 2.1.4
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Labels: json, mysql
> Fix For: 2.1.5, 3.0.0
>
>
> There are some errors in the predefined configuration, which prevent normal
> Core startup, as some classes ({{Conf, CPlainAttr, CPlainAttrValue,
> CPlainAttrUniqueValue}}) are not defined when MySQL with JSON support is
> enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1469) MySQL with JSON support: errors during startup
[
https://issues.apache.org/jira/browse/SYNCOPE-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834433#comment-16834433
]
Francesco Chicchiriccò commented on SYNCOPE-1469:
-
Workaround: use the following files instead of the ones from release 2.1.4:
*
https://github.com/apache/syncope/blob/2_1_X/core/persistence-jpa-json/src/main/resources/META-INF/spring-orm-myjson.xml
*
https://github.com/apache/syncope/blob/2_1_X/core/persistence-jpa-json/src/main/resources/myjson/indexes.xml
> MySQL with JSON support: errors during startup
> --
>
> Key: SYNCOPE-1469
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1469
> Project: Syncope
> Issue Type: Bug
> Components: core, docker
>Affects Versions: 2.1.4
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Labels: json, mysql
> Fix For: 2.1.5, 3.0.0
>
>
> There are some errors in the predefined configuration, which prevent normal
> Core startup, as some classes ({{Conf, CPlainAttr, CPlainAttrValue,
> CPlainAttrUniqueValue}}) are not defined when MySQL with JSON support is
> enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1469) MySQL with JSON support: errors during startup
[
https://issues.apache.org/jira/browse/SYNCOPE-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834428#comment-16834428
]
ASF subversion and git services commented on SYNCOPE-1469:
--
Commit 4d974d6585be3b812620c69e00c9a36fc2a108e8 in syncope's branch
refs/heads/2_1_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=4d974d6 ]
[SYNCOPE-1469] Removing missing tables from configuration
> MySQL with JSON support: errors during startup
> --
>
> Key: SYNCOPE-1469
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1469
> Project: Syncope
> Issue Type: Bug
> Components: core, docker
>Affects Versions: 2.1.4
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Labels: json, mysql
> Fix For: 2.1.5, 3.0.0
>
>
> There are some errors in the predefined configuration, which prevent normal
> Core startup, as some classes ({{Conf, CPlainAttr, CPlainAttrValue,
> CPlainAttrUniqueValue}}) are not defined when MySQL with JSON support is
> enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1469) MySQL with JSON support: errors during startup
[
https://issues.apache.org/jira/browse/SYNCOPE-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-1469.
-
Resolution: Fixed
> MySQL with JSON support: errors during startup
> --
>
> Key: SYNCOPE-1469
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1469
> Project: Syncope
> Issue Type: Bug
> Components: core, docker
>Affects Versions: 2.1.4
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Labels: json, mysql
> Fix For: 2.1.5, 3.0.0
>
>
> There are some errors in the predefined configuration, which prevent normal
> Core startup, as some classes ({{Conf, CPlainAttr, CPlainAttrValue,
> CPlainAttrUniqueValue}}) are not defined when MySQL with JSON support is
> enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SYNCOPE-1469) MySQL with JSON support: errors during startup
Francesco Chicchiriccò created SYNCOPE-1469:
---
Summary: MySQL with JSON support: errors during startup
Key: SYNCOPE-1469
URL: https://issues.apache.org/jira/browse/SYNCOPE-1469
Project: Syncope
Issue Type: Bug
Components: core, docker
Affects Versions: 2.1.4
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
Fix For: 2.1.5, 3.0.0
There are some errors in the predefined configuration, which prevent normal
Core startup, as some classes ({{Conf, CPlainAttr, CPlainAttrValue,
CPlainAttrUniqueValue}}) are not defined when MySQL with JSON support is
enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
