[jira] [Updated] (SYNCOPE-360) Removing Role mapping from External Resource fails
[ https://issues.apache.org/jira/browse/SYNCOPE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-360: --- Fix Version/s: 1.2.0 1.1.1 Removing Role mapping from External Resource fails -- Key: SYNCOPE-360 URL: https://issues.apache.org/jira/browse/SYNCOPE-360 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.0 Environment: Linux/Tomcat Reporter: Martin van Es Fix For: 1.1.1, 1.2.0 Today I was experimenting with role assignment and tried to map internal ROLE/RoleId to a column in my synchronisation CSVdir resource. While syncing I got an error of Objectclasses not matching so I wanted to remove this relationship by clicking the checkbox in from of it, which succeeded. But after saving the new settings and inspecting the resource role mapping, the old role relation was still there, effectively leaving me with a broken resource. I had to manually remove the role map using my database gui to be able to use the resource again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-360) Removing Role mapping from External Resource fails
[ https://issues.apache.org/jira/browse/SYNCOPE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636118#comment-13636118 ] Francesco Chicchiriccò commented on SYNCOPE-360: You have got the original failure while trying to sync roles from the CSVDir resource because the CSVDir ConnId connector is only able to manage users, not roles. I will try to reproduce the problem you had in the admin console and let you know. Removing Role mapping from External Resource fails -- Key: SYNCOPE-360 URL: https://issues.apache.org/jira/browse/SYNCOPE-360 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.0 Environment: Linux/Tomcat Reporter: Martin van Es Fix For: 1.1.1, 1.2.0 Today I was experimenting with role assignment and tried to map internal ROLE/RoleId to a column in my synchronisation CSVdir resource. While syncing I got an error of Objectclasses not matching so I wanted to remove this relationship by clicking the checkbox in from of it, which succeeded. But after saving the new settings and inspecting the resource role mapping, the old role relation was still there, effectively leaving me with a broken resource. I had to manually remove the role map using my database gui to be able to use the resource again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (SYNCOPE-361) When creating new report, the modal window does not close and an exception is logged
Francesco Chicchiriccò created SYNCOPE-361: -- Summary: When creating new report, the modal window does not close and an exception is logged Key: SYNCOPE-361 URL: https://issues.apache.org/jira/browse/SYNCOPE-361 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.1, 1.2.0 When creating new report from the admin console, everything goes smooth until the Save button is pressed:at that point the modal window does not close and an exception is logged. The new report, however, is correctly created. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SYNCOPE-361) When creating new report, the modal window does not close and an exception is logged
[ https://issues.apache.org/jira/browse/SYNCOPE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-361. Resolution: Fixed 1_1_X: http://svn.apache.org/r1469739 trunk: http://svn.apache.org/r1469740 When creating new report, the modal window does not close and an exception is logged Key: SYNCOPE-361 URL: https://issues.apache.org/jira/browse/SYNCOPE-361 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.1, 1.2.0 When creating new report from the admin console, everything goes smooth until the Save button is pressed:at that point the modal window does not close and an exception is logged. The new report, however, is correctly created. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (SYNCOPE-360) Removing Role mapping from External Resource fails
[ https://issues.apache.org/jira/browse/SYNCOPE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-360: -- Assignee: Francesco Chicchiriccò Removing Role mapping from External Resource fails -- Key: SYNCOPE-360 URL: https://issues.apache.org/jira/browse/SYNCOPE-360 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.0 Environment: Linux/Tomcat Reporter: Martin van Es Assignee: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 Today I was experimenting with role assignment and tried to map internal ROLE/RoleId to a column in my synchronisation CSVdir resource. While syncing I got an error of Objectclasses not matching so I wanted to remove this relationship by clicking the checkbox in from of it, which succeeded. But after saving the new settings and inspecting the resource role mapping, the old role relation was still there, effectively leaving me with a broken resource. I had to manually remove the role map using my database gui to be able to use the resource again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (SYNCOPE-362) Disable mapping tab when the underlying connector does not support correspondent ObjectClass
Francesco Chicchiriccò created SYNCOPE-362: -- Summary: Disable mapping tab when the underlying connector does not support correspondent ObjectClass Key: SYNCOPE-362 URL: https://issues.apache.org/jira/browse/SYNCOPE-362 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Fix For: 1.1.1 If a given connector supports ObjectClass.ACCOUNT, enable the User mapping tab, otherwise keep it disabled. If a given connector supports ObjectClass.GROUP, enable the Role mapping tab, otherwise keep it disabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Console Log Settings lost after Syncope restart
Hi Syncopers, I'm using Syncope 1.0.7. I have seen that changing log levels of Console are lost after a Syncope restart while Core Log changes are maintaned. It's correct? Regards, Denis.
[jira] [Created] (SYNCOPE-363) ApacheDS not available since second run of the standalone distribution
Francesco Chicchiriccò created SYNCOPE-363: -- Summary: ApacheDS not available since second run of the standalone distribution Key: SYNCOPE-363 URL: https://issues.apache.org/jira/browse/SYNCOPE-363 Project: Syncope Issue Type: Bug Components: build-tools, standalone Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 When starting the standalone distribution, from the second time on the build-tools webapp will refuse to start, leaving Syncope without connectors. This happens since the ApacheDSStartStopListener fails creating its work directory - that is actually already there, used during the first run. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Console Log Settings lost after Syncope restart
On 19/04/2013 11:21, Denis Signoretto wrote: Hi Syncopers, I'm using Syncope 1.0.7. I have seen that changing log levels of Console are lost after a Syncope restart while Core Log changes are maintaned. It's correct? It is expected: console log settings are only dependent con console's logback.xml. Regards. -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
[jira] [Resolved] (SYNCOPE-360) Removing Role mapping from External Resource fails
[ https://issues.apache.org/jira/browse/SYNCOPE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-360. Resolution: Fixed 1_1_X: http://svn.apache.org/r1469758 trunk: http://svn.apache.org/r1469759 Removing Role mapping from External Resource fails -- Key: SYNCOPE-360 URL: https://issues.apache.org/jira/browse/SYNCOPE-360 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.0 Environment: Linux/Tomcat Reporter: Martin van Es Assignee: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 Today I was experimenting with role assignment and tried to map internal ROLE/RoleId to a column in my synchronisation CSVdir resource. While syncing I got an error of Objectclasses not matching so I wanted to remove this relationship by clicking the checkbox in from of it, which succeeded. But after saving the new settings and inspecting the resource role mapping, the old role relation was still there, effectively leaving me with a broken resource. I had to manually remove the role map using my database gui to be able to use the resource again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SYNCOPE-362) Disable mapping tab when the underlying connector does not support correspondent ObjectClass
[ https://issues.apache.org/jira/browse/SYNCOPE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-362: --- Component/s: core Disable mapping tab when the underlying connector does not support correspondent ObjectClass Key: SYNCOPE-362 URL: https://issues.apache.org/jira/browse/SYNCOPE-362 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1 If a given connector supports ObjectClass.ACCOUNT, enable the User mapping tab, otherwise keep it disabled. If a given connector supports ObjectClass.GROUP, enable the Role mapping tab, otherwise keep it disabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (SYNCOPE-362) Disable mapping tab when the underlying connector does not support correspondent ObjectClass
[ https://issues.apache.org/jira/browse/SYNCOPE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-362: -- Assignee: Francesco Chicchiriccò Disable mapping tab when the underlying connector does not support correspondent ObjectClass Key: SYNCOPE-362 URL: https://issues.apache.org/jira/browse/SYNCOPE-362 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1 If a given connector supports ObjectClass.ACCOUNT, enable the User mapping tab, otherwise keep it disabled. If a given connector supports ObjectClass.GROUP, enable the Role mapping tab, otherwise keep it disabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
R: Console Log Settings lost after Syncope restart
At first I thought it wasn't so intuitive for an administrator. After same thought I agree with the choice. Console it's a separate component and don't depends on db, so it's a good idea leave his settings separated by syncope core. (I guess this is the main reason behind this choice). I have added some info about it at the documentation [1]. Feel free to adjust it. Regards, Denis. [1] - https://cwiki.apache.org/confluence/display/SYNCOPE/Log+levels -Messaggio originale- Da: Francesco Chicchiriccò [mailto:ilgro...@apache.org] Inviato: venerdì 19 aprile 2013 11:38 A: dev@syncope.apache.org Oggetto: Re: Console Log Settings lost after Syncope restart On 19/04/2013 11:21, Denis Signoretto wrote: Hi Syncopers, I'm using Syncope 1.0.7. I have seen that changing log levels of Console are lost after a Syncope restart while Core Log changes are maintaned. It's correct? It is expected: console log settings are only dependent con console's logback.xml. Regards. -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
[jira] [Resolved] (SYNCOPE-362) Disable mapping tab when the underlying connector does not support correspondent ObjectClass
[ https://issues.apache.org/jira/browse/SYNCOPE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-362. Resolution: Fixed 1_1_X: http://svn.apache.org/r1469812 trunk: http://svn.apache.org/r1469814 Disable mapping tab when the underlying connector does not support correspondent ObjectClass Key: SYNCOPE-362 URL: https://issues.apache.org/jira/browse/SYNCOPE-362 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1 If a given connector supports ObjectClass.ACCOUNT, enable the User mapping tab, otherwise keep it disabled. If a given connector supports ObjectClass.GROUP, enable the Role mapping tab, otherwise keep it disabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (SYNCOPE-363) ApacheDS not available since second run of the standalone distribution
[ https://issues.apache.org/jira/browse/SYNCOPE-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-363: -- Assignee: Francesco Chicchiriccò ApacheDS not available since second run of the standalone distribution -- Key: SYNCOPE-363 URL: https://issues.apache.org/jira/browse/SYNCOPE-363 Project: Syncope Issue Type: Bug Components: build-tools, standalone Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 When starting the standalone distribution, from the second time on the build-tools webapp will refuse to start, leaving Syncope without connectors. This happens since the ApacheDSStartStopListener fails creating its work directory - that is actually already there, used during the first run. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Apache Syncope 1.0.8
+1. Colm. On Thu, Apr 18, 2013 at 12:34 PM, Massimiliano Perrone massimiliano.perr...@tirasa.net wrote: +1 Il 18/04/2013 11:05, Francesco Chicchiriccò ha scritto: I've created a 1.0.8 release, with the following artifacts up for a vote: SVN source tag (r1469201): https://svn.apache.org/repos/**asf/syncope/tags/syncope-1.0.**8/https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.8/ List of changes: https://svn.apache.org/repos/**asf/syncope/tags/syncope-1.0.**8/CHANGEShttps://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.8/CHANGES Maven staging repo: https://repository.apache.org/**content/repositories/** orgapachesyncope-116/https://repository.apache.org/content/repositories/orgapachesyncope-116/ Source release (checksums and signatures are available at the same location): https://repository.apache.org/**content/repositories/** orgapachesyncope-116/org/**apache/syncope/syncope-root/1.** 0.8/syncope-root-1.0.8-source-**release.ziphttps://repository.apache.org/content/repositories/orgapachesyncope-116/org/apache/syncope/syncope-root/1.0.8/syncope-root-1.0.8-source-release.zip Staging site: http://syncope.apache.org/1.0.**8/ http://syncope.apache.org/1.0.8/ PGP release keys (signed using 273DF287): http://www.apache.org/dist/**syncope/KEYShttp://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Massimiliano Perrone Tel +39 393 9121310 Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member http://people.apache.org/~**massi/ http://people.apache.org/~massi/ L'apprendere molte cose non insegna l'intelligenza (Eraclito) -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: R: Console Log Settings lost after Syncope restart
On 19/04/2013 12:48, Denis Signoretto wrote: At first I thought it wasn't so intuitive for an administrator. After same thought I agree with the choice. Console it's a separate component and don't depends on db, so it's a good idea leave his settings separated by syncope core. (I guess this is the main reason behind this choice). Correct :-) I have added some info about it at the documentation [1]. Feel free to adjust it. Thanks! Regards. [1] - https://cwiki.apache.org/confluence/display/SYNCOPE/Log+levels -Messaggio originale- Da: Francesco Chicchiriccò [mailto:ilgro...@apache.org] Inviato: venerdì 19 aprile 2013 11:38 A: dev@syncope.apache.org Oggetto: Re: Console Log Settings lost after Syncope restart On 19/04/2013 11:21, Denis Signoretto wrote: Hi Syncopers, I'm using Syncope 1.0.7. I have seen that changing log levels of Console are lost after a Syncope restart while Core Log changes are maintaned. It's correct? It is expected: console log settings are only dependent con console's logback.xml. -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
[jira] [Resolved] (SYNCOPE-363) ApacheDS not available since second run of the standalone distribution
[ https://issues.apache.org/jira/browse/SYNCOPE-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-363. Resolution: Fixed 1_1_X: http://svn.apache.org/r1469830 trunk: http://svn.apache.org/r1469831 ApacheDS not available since second run of the standalone distribution -- Key: SYNCOPE-363 URL: https://issues.apache.org/jira/browse/SYNCOPE-363 Project: Syncope Issue Type: Bug Components: build-tools, standalone Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 When starting the standalone distribution, from the second time on the build-tools webapp will refuse to start, leaving Syncope without connectors. This happens since the ApacheDSStartStopListener fails creating its work directory - that is actually already there, used during the first run. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (SYNCOPE-364) Rejected users are anyway propagate to associated resources
Francesco Chicchiriccò created SYNCOPE-364: -- Summary: Rejected users are anyway propagate to associated resources Key: SYNCOPE-364 URL: https://issues.apache.org/jira/browse/SYNCOPE-364 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.0, 1.0.8 Reporter: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 Using the default worklfow, when an user is created with an external resource, goes through approval and is rejected, a propagation towards the given external resource is anyway performed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SYNCOPE-345) You need to click the Execute synchronization task twice
[ https://issues.apache.org/jira/browse/SYNCOPE-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-345: --- Fix Version/s: (was: 1.1.1) You need to click the Execute synchronization task twice Key: SYNCOPE-345 URL: https://issues.apache.org/jira/browse/SYNCOPE-345 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.0 Reporter: jordi Priority: Minor You need to click the Execute button twice to execute a synchronization task from the admin console. The first click is not registered. The second one is. Issue occurs in a least Safari, Chrome and Firefox. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SYNCOPE-364) Rejected users are anyway propagate to associated resources
[ https://issues.apache.org/jira/browse/SYNCOPE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-364: --- Fix Version/s: 1.0.9 Rejected users are anyway propagate to associated resources --- Key: SYNCOPE-364 URL: https://issues.apache.org/jira/browse/SYNCOPE-364 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.8, 1.1.0 Reporter: Francesco Chicchiriccò Fix For: 1.0.9, 1.1.1, 1.2.0 Using the default worklfow, when an user is created with an external resource, goes through approval and is rejected, a propagation towards the given external resource is anyway performed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SYNCOPE-364) Rejected users are anyway propagate to associated resources
[ https://issues.apache.org/jira/browse/SYNCOPE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-364. Resolution: Fixed 1_0_X: http://svn.apache.org/r1469875 1_1_X: http://svn.apache.org/r1469880 trunk: http://svn.apache.org/r1469883 Rejected users are anyway propagate to associated resources --- Key: SYNCOPE-364 URL: https://issues.apache.org/jira/browse/SYNCOPE-364 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.8, 1.1.0 Reporter: Francesco Chicchiriccò Fix For: 1.0.9, 1.1.1, 1.2.0 Using the default worklfow, when an user is created with an external resource, goes through approval and is rejected, a propagation towards the given external resource is anyway performed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-361) When creating new report, the modal window does not close and an exception is logged
[ https://issues.apache.org/jira/browse/SYNCOPE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636687#comment-13636687 ] Hudson commented on SYNCOPE-361: Integrated in Syncope-1_1_X #22 (See [https://builds.apache.org/job/Syncope-1_1_X/22/]) [SYNCOPE-361] Handling mapping reset (Revision 1469758) [SYNCOPE-361] Fixing ReportService#create invocation (Revision 1469739) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/ResourceModalPage.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceMappingPanel.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/data/ResourceDataBinder.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/persistence/relationships/ResourceTest.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/ResourceTestITCase.java ilgrosso : Files : * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/rest/ReportRestClient.java When creating new report, the modal window does not close and an exception is logged Key: SYNCOPE-361 URL: https://issues.apache.org/jira/browse/SYNCOPE-361 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.1, 1.2.0 When creating new report from the admin console, everything goes smooth until the Save button is pressed:at that point the modal window does not close and an exception is logged. The new report, however, is correctly created. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-362) Disable mapping tab when the underlying connector does not support correspondent ObjectClass
[ https://issues.apache.org/jira/browse/SYNCOPE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636686#comment-13636686 ] Hudson commented on SYNCOPE-362: Integrated in Syncope-1_1_X #22 (See [https://builds.apache.org/job/Syncope-1_1_X/22/]) [SYNCOPE-362] Added new REST method for enquerying supported ConnId object classes + used such method from admin console to enable / disable related schema mapping (Revision 1469812) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/client/src/main/java/org/apache/syncope/client/services/proxy/ConnectorServiceProxy.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/services/ConnectorService.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/to/ConnIdObjectClassTO.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/types/AuditElements.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceDetailsPanel.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceMappingPanel.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/rest/ConnectorRestClient.java * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/panels/ResourceDetailsPanel.html * /syncope/branches/1_1_X/core/pom.xml * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/Connector.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/impl/AsyncConnectorFacade.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/impl/ConnectorFacadeProxy.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/controller/ConnInstanceController.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/services/ConnectorServiceImpl.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/ConnInstanceTestITCase.java Disable mapping tab when the underlying connector does not support correspondent ObjectClass Key: SYNCOPE-362 URL: https://issues.apache.org/jira/browse/SYNCOPE-362 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 If a given connector supports ObjectClass.ACCOUNT, enable the User mapping tab, otherwise keep it disabled. If a given connector supports ObjectClass.GROUP, enable the Role mapping tab, otherwise keep it disabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-364) Rejected users are anyway propagate to associated resources
[ https://issues.apache.org/jira/browse/SYNCOPE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636688#comment-13636688 ] Hudson commented on SYNCOPE-364: Integrated in Syncope-1_1_X #22 (See [https://builds.apache.org/job/Syncope-1_1_X/22/]) [SYNCOPE-364] Merge from 1_0_X (Revision 1469880) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X * /syncope/branches/1_1_X/CHANGES * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/controller/UserController.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/workflow/user/activiti/ActivitiUserWorkflowAdapter.java * /syncope/branches/1_1_X/core/src/main/resources/userWorkflow.bpmn20.xml * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java Rejected users are anyway propagate to associated resources --- Key: SYNCOPE-364 URL: https://issues.apache.org/jira/browse/SYNCOPE-364 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.8, 1.1.0 Reporter: Francesco Chicchiriccò Fix For: 1.0.9, 1.1.1, 1.2.0 Using the default worklfow, when an user is created with an external resource, goes through approval and is rejected, a propagation towards the given external resource is anyway performed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-363) ApacheDS not available since second run of the standalone distribution
[ https://issues.apache.org/jira/browse/SYNCOPE-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636689#comment-13636689 ] Hudson commented on SYNCOPE-363: Integrated in Syncope-1_1_X #22 (See [https://builds.apache.org/job/Syncope-1_1_X/22/]) [SYNCOPE-363] Creating ApacheDS work directory and loading default content only for first run (Revision 1469830) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/build-tools/src/main/java/org/apache/syncope/buildtools/ApacheDSStartStopListener.java ApacheDS not available since second run of the standalone distribution -- Key: SYNCOPE-363 URL: https://issues.apache.org/jira/browse/SYNCOPE-363 Project: Syncope Issue Type: Bug Components: build-tools, standalone Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 When starting the standalone distribution, from the second time on the build-tools webapp will refuse to start, leaving Syncope without connectors. This happens since the ApacheDSStartStopListener fails creating its work directory - that is actually already there, used during the first run. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-362) Disable mapping tab when the underlying connector does not support correspondent ObjectClass
[ https://issues.apache.org/jira/browse/SYNCOPE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636692#comment-13636692 ] Hudson commented on SYNCOPE-362: Integrated in Syncope-trunk #200 (See [https://builds.apache.org/job/Syncope-trunk/200/]) [SYNCOPE-362] Merge from 1_1_X (Revision 1469814) Result = SUCCESS ilgrosso : Files : * /syncope/trunk * /syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/ConnectorServiceProxy.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ConnectorService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/ConnIdObjectClassTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/AuditElements.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceDetailsPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceMappingPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/ConnectorRestClient.java * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/panels/ResourceDetailsPanel.html * /syncope/trunk/core/pom.xml * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/Connector.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/AsyncConnectorFacade.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/ConnectorFacadeProxy.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/ConnInstanceController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ConnectorServiceImpl.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ConnInstanceTestITCase.java Disable mapping tab when the underlying connector does not support correspondent ObjectClass Key: SYNCOPE-362 URL: https://issues.apache.org/jira/browse/SYNCOPE-362 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 If a given connector supports ObjectClass.ACCOUNT, enable the User mapping tab, otherwise keep it disabled. If a given connector supports ObjectClass.GROUP, enable the Role mapping tab, otherwise keep it disabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-364) Rejected users are anyway propagate to associated resources
[ https://issues.apache.org/jira/browse/SYNCOPE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636694#comment-13636694 ] Hudson commented on SYNCOPE-364: Integrated in Syncope-trunk #200 (See [https://builds.apache.org/job/Syncope-trunk/200/]) [SYNCOPE-364] Merge from 1_1_X (Revision 1469883) Result = SUCCESS ilgrosso : Files : * /syncope/trunk * /syncope/trunk/CHANGES * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/UserController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/activiti/ActivitiUserWorkflowAdapter.java * /syncope/trunk/core/src/main/resources/userWorkflow.bpmn20.xml * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java Rejected users are anyway propagate to associated resources --- Key: SYNCOPE-364 URL: https://issues.apache.org/jira/browse/SYNCOPE-364 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.8, 1.1.0 Reporter: Francesco Chicchiriccò Fix For: 1.0.9, 1.1.1, 1.2.0 Using the default worklfow, when an user is created with an external resource, goes through approval and is rejected, a propagation towards the given external resource is anyway performed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-363) ApacheDS not available since second run of the standalone distribution
[ https://issues.apache.org/jira/browse/SYNCOPE-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636695#comment-13636695 ] Hudson commented on SYNCOPE-363: Integrated in Syncope-trunk #200 (See [https://builds.apache.org/job/Syncope-trunk/200/]) [SYNCOPE-363] Merge from 1_1_X (Revision 1469831) Result = SUCCESS ilgrosso : Files : * /syncope/trunk * /syncope/trunk/build-tools/src/main/java/org/apache/syncope/buildtools/ApacheDSStartStopListener.java ApacheDS not available since second run of the standalone distribution -- Key: SYNCOPE-363 URL: https://issues.apache.org/jira/browse/SYNCOPE-363 Project: Syncope Issue Type: Bug Components: build-tools, standalone Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 When starting the standalone distribution, from the second time on the build-tools webapp will refuse to start, leaving Syncope without connectors. This happens since the ApacheDSStartStopListener fails creating its work directory - that is actually already there, used during the first run. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Syncope-1_0_X - Build # 191 - Failure
The Apache Jenkins build system has built Syncope-1_0_X (build #191) Status: Failure Check console output at https://builds.apache.org/job/Syncope-1_0_X/191/ to view the results.
[jira] [Commented] (SYNCOPE-364) Rejected users are anyway propagate to associated resources
[ https://issues.apache.org/jira/browse/SYNCOPE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636884#comment-13636884 ] Hudson commented on SYNCOPE-364: Integrated in Syncope-1_0_X #191 (See [https://builds.apache.org/job/Syncope-1_0_X/191/]) [SYNCOPE-364] Disabling propagation from workflow definition (Revision 1469875) Result = FAILURE ilgrosso : Files : * /syncope/branches/1_0_X/core/src/main/java/org/apache/syncope/core/rest/controller/UserController.java * /syncope/branches/1_0_X/core/src/main/resources/userWorkflow.bpmn20.xml * /syncope/branches/1_0_X/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java Rejected users are anyway propagate to associated resources --- Key: SYNCOPE-364 URL: https://issues.apache.org/jira/browse/SYNCOPE-364 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.8, 1.1.0 Reporter: Francesco Chicchiriccò Fix For: 1.0.9, 1.1.1, 1.2.0 Using the default worklfow, when an user is created with an external resource, goes through approval and is rejected, a propagation towards the given external resource is anyway performed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
