Re: [VOTE] Apache Syncope 3.0.7 2nd attempt
+1 Regards On Mon, May 20, 2024 at 9:15 AM Francesco Chicchiriccò wrote: > I've created a 3.0.7 release, with the following artifacts up for a vote: > > GIT source tag (f0a9c658c7): > https://github.com/apache/syncope/releases/tag/syncope-3.0.7 > > List of changes: > https://github.com/apache/syncope/blob/syncope-3.0.7/CHANGES > > Staging artifacts: > https://dist.apache.org/repos/dist/dev/syncope/3.0.7/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachesyncope-1088/ > > Staging site: > https://syncope.apache.org/3.0.7/index.html > > PGP release keys (signed using 273DF287): > http://www.apache.org/dist/syncope/KEYS > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my +1 > Regards. > > > >
[jira] [Resolved] (SYNCOPE-1816) Provide the possibility to add a JcifsSpnegoAuthenticationHandler
[ https://issues.apache.org/jira/browse/SYNCOPE-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabio Martelli resolved SYNCOPE-1816. - Resolution: Fixed > Provide the possibility to add a JcifsSpnegoAuthenticationHandler > - > > Key: SYNCOPE-1816 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1816 > Project: Syncope > Issue Type: Improvement > Components: console, core, wa >Affects Versions: 3.0.6 > Reporter: Fabio Martelli > Assignee: Fabio Martelli >Priority: Minor > Fix For: 3.0.7, 4.0.0 > > > Provide the possibility to add JcifsSpnegoAuthenticationHandler -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1816) Provide the possibility to add a JcifsSpnegoAuthenticationHandler
Fabio Martelli created SYNCOPE-1816: --- Summary: Provide the possibility to add a JcifsSpnegoAuthenticationHandler Key: SYNCOPE-1816 URL: https://issues.apache.org/jira/browse/SYNCOPE-1816 Project: Syncope Issue Type: Improvement Components: console, core, wa Affects Versions: 3.0.6 Reporter: Fabio Martelli Assignee: Fabio Martelli Fix For: 3.0.7 Provide the possibility to add JcifsSpnegoAuthenticationHandler -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1814) Cannot specify notification/audit user events working fine
Fabio Martelli created SYNCOPE-1814: --- Summary: Cannot specify notification/audit user events working fine Key: SYNCOPE-1814 URL: https://issues.apache.org/jira/browse/SYNCOPE-1814 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 2.1.14 Reporter: Fabio Martelli Fix For: 2.1.15 If you want to specify a notification event on a propagation task you cannot give a configuration working fine because entity could be specified just in lowercase but matched in uppercase by the core (by using AnyTypeKind object). For instance, the following is what the core tries to match in order to verify the notification availability [PropagationTask]:[USER]:[AD]:[create]:[FAILURE] But the rule that you can specify via console is just the following (note user in lowercase instead of uppercase) [PropagationTask]:[user]:[AD]:[create]:[FAILURE] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1802) Missing delegated SAML2 IdP configuration parameters
[ https://issues.apache.org/jira/browse/SYNCOPE-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabio Martelli resolved SYNCOPE-1802. - Resolution: Fixed > Missing delegated SAML2 IdP configuration parameters > > > Key: SYNCOPE-1802 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1802 > Project: Syncope > Issue Type: Improvement > Components: common, wa >Affects Versions: 3.0.6 > Reporter: Fabio Martelli > Assignee: Fabio Martelli >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > Missing parameters serviceProviderMetadataPath and responsesSigned. > Missing mapping for KeystorePath and WantsAssertionsSigned. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1802) Missing delegated SAML2 IdP configuration parameter
Fabio Martelli created SYNCOPE-1802: --- Summary: Missing delegated SAML2 IdP configuration parameter Key: SYNCOPE-1802 URL: https://issues.apache.org/jira/browse/SYNCOPE-1802 Project: Syncope Issue Type: Improvement Components: common, wa Affects Versions: 3.0.6 Reporter: Fabio Martelli Fix For: 3.0.7 Missing parameters serviceProviderMetadataPath and responsesSigned. Missing mapping for KeystorePath and WantsAssertionsSigned. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1778) Reset password requires double click in order to provide username
[ https://issues.apache.org/jira/browse/SYNCOPE-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabio Martelli resolved SYNCOPE-1778. - Resolution: Fixed > Reset password requires double click in order to provide username > - > > Key: SYNCOPE-1778 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1778 > Project: Syncope > Issue Type: Bug > Components: enduser >Affects Versions: 3.0.5 > Reporter: Fabio Martelli > Assignee: Fabio Martelli >Priority: Major > Fix For: 3.0.6, 4.0.0 > > > In case of no security question, reset password requires double click in > order to provide username. > > The problem is > [here|https://github.com/apache/syncope/blob/syncope-3.0.5/client/idrepo/enduser/src/main/java/org/apache/syncope/client/enduser/pages/SelfPasswordReset.java#L154] > Replacing AjaxFormComponentUpdatingBehavior with > IndicatorAjaxFormComponentUpdatingBehavior solves the problem -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1778) Reset password requires double click in order to provide username
Fabio Martelli created SYNCOPE-1778: --- Summary: Reset password requires double click in order to provide username Key: SYNCOPE-1778 URL: https://issues.apache.org/jira/browse/SYNCOPE-1778 Project: Syncope Issue Type: Bug Components: enduser Affects Versions: 3.0.5 Reporter: Fabio Martelli Assignee: Fabio Martelli Fix For: 3.0.6 In case of no security question, reset password requires double click in order to provide username. The problem is [here|https://github.com/apache/syncope/blob/syncope-3.0.5/client/idrepo/enduser/src/main/java/org/apache/syncope/client/enduser/pages/SelfPasswordReset.java#L154] Reoplacing AjaxFormComponentUpdatingBehavior with IndicatorAjaxFormComponentUpdatingBehavior solve the problem -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] Apache Syncope 3.0.4
+1 Regards On Fri, Jul 7, 2023 at 10:11 AM Francesco Chicchiriccò wrote: > I've created a 3.0.4 release, with the following artifacts up for a vote: > > GIT source tag (eff73b0772): > https://github.com/apache/syncope/releases/tag/syncope-3.0.4 > > List of changes: > https://github.com/apache/syncope/blob/syncope-3.0.4/CHANGES > > Staging artifacts: > https://dist.apache.org/repos/dist/dev/syncope/3.0.4/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachesyncope-1083/ > > Staging site: > https://syncope.apache.org/3.0.4/index.html > > PGP release keys (signed using 273DF287): > http://www.apache.org/dist/syncope/KEYS > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my +1 > Regards. > > -- > 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] [Updated] (SYNCOPE-1763) Constant increase of open files after upgrade to CXF 3.6.0
[
https://issues.apache.org/jira/browse/SYNCOPE-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabio Martelli updated SYNCOPE-1763:
Description:
Just after the upgrade of CXF from 3.5.6 to 3.6.0 (commit
2252d74209bb944d90dd20579c2468597e4f79f3) opened FDs increase in number without
ever decreasing.
This behaviour occour evrytime a cxf request is performed towards the Core
component.
This issue has been discovered investigating a "Too many open files" exception
raised by WA component during delete expiring gauth tokens job execution.
Generally, considering an execution of this jov every 35 seconds, after 16
hours, more or less, WA becomes completely unavailable cause this issue.
The issue has been reproduced in the embedded env and analized by lsof tool.
This is an example before the commit above
{code}
$ while [ 1 ]; do sudo lsof -u fabio 2> /dev/null | grep 54201| grep pipe | wc
-l; sleep 60; done
17
17
17
17
17{code}
and the following, the behaviour just after
{code}
$ while [ 1 ]; do sudo lsof -u fabio 2> /dev/null | grep 45581| grep pipe | wc
-l; sleep 60; done
157
179
183
185
189{code}
As you can see the difference is evident.
was:
Just after the upgrade of CXF from 3.5.6 to 3.6.0 (commit
[2252d74209bb944d90dd20579c2468597e4f79f3|https://github.com/apache/syncope/commit/2252d74209bb944d90dd20579c2468597e4f79f3])
the number of open FDs is in constant increase.
This behaviour occours everytime an REST request is performed against the Core
component.
This issue has been discovered investigating a "Too many open files" exception
raised by WA component during delete expiring gauth tokens job execution.
Generally, considering an execution of this jov every 35 seconds, after 16
hours, more or less, WA becomes completely unavailable cause this issue.
The issue has been reproduced in the embedded env and analized by lsof tool.
This is an example before the commit above
{code:java}
$ while [ 1 ]; do sudo lsof -u fabio 2> /dev/null | grep 54201| grep pipe | wc
-l; sleep 60; done 17 17
17
17
17{code}
and the following, the behaviour just after
{code:java}
$ while [ 1 ]; do sudo lsof -u fabio 2> /dev/null | grep 45581| grep pipe | wc
-l; sleep 60; done
157
179
183
185
189{code}
As you can see the difference is evident.
> Constant increase of open files after upgrade to CXF 3.6.0
> --
>
> Key: SYNCOPE-1763
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1763
> Project: Syncope
> Issue Type: Bug
> Components: client
>Affects Versions: 3.0.4
>Reporter: Fabio Martelli
>Priority: Major
> Fix For: 3.0.4, 4.0.0
>
>
> Just after the upgrade of CXF from 3.5.6 to 3.6.0 (commit
> 2252d74209bb944d90dd20579c2468597e4f79f3) opened FDs increase in number
> without ever decreasing.
> This behaviour occour evrytime a cxf request is performed towards the Core
> component.
>
> This issue has been discovered investigating a "Too many open files"
> exception raised by WA component during delete expiring gauth tokens job
> execution. Generally, considering an execution of this jov every 35 seconds,
> after 16 hours, more or less, WA becomes completely unavailable cause this
> issue.
>
> The issue has been reproduced in the embedded env and analized by lsof tool.
> This is an example before the commit above
> {code}
> $ while [ 1 ]; do sudo lsof -u fabio 2> /dev/null | grep 54201| grep pipe |
> wc -l; sleep 60; done
> 17
> 17
> 17
> 17
> 17{code}
> and the following, the behaviour just after
> {code}
> $ while [ 1 ]; do sudo lsof -u fabio 2> /dev/null | grep 45581| grep pipe |
> wc -l; sleep 60; done
> 157
> 179
> 183
> 185
> 189{code}
> As you can see the difference is evident.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SYNCOPE-1763) CXF 3.6.0 cause increasing of opened files without ever decrease
Fabio Martelli created SYNCOPE-1763:
---
Summary: CXF 3.6.0 cause increasing of opened files without ever
decrease
Key: SYNCOPE-1763
URL: https://issues.apache.org/jira/browse/SYNCOPE-1763
Project: Syncope
Issue Type: Improvement
Components: console, enduser, sra, wa
Affects Versions: 3.0.4
Reporter: Fabio Martelli
Fix For: 3.0.4, 4.0.0
Just after the upgrade of CXF from 3.5.6 to 3.6.0 (commit
2252d74209bb944d90dd20579c2468597e4f79f3) opened FDs increase in number without
ever decreasing.
This behaviour occour evrytime a cxf request is performed towards the Core
component.
This issue has been discovered investigating a "Too many open files" exception
raised by WA component during delete expiring gauth tokens job execution.
Generally, considering an execution of this jov every 35 seconds, after 16
hours, more or less, WA becomes completely unavailable cause this issue.
The issue has been reproduced in the embedded env and analized by lsof tool.
This is an example before the commit above
{code:java}
$ while [ 1 ]; do sudo lsof -u fabio 2> /dev/null | grep 54201| grep pipe | wc
-l; sleep 60; done 17 17
17
17
17{code}
and the following, the behaviour just after
{code:java}
$ while [ 1 ]; do sudo lsof -u fabio 2> /dev/null | grep 45581| grep pipe | wc
-l; sleep 60; done
157
179
183
185
189{code}
As you can see the difference is evident.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SYNCOPE-1758) NullPointer exception at WA refresh time during startup
Fabio Martelli created SYNCOPE-1758:
---
Summary: NullPointer exception at WA refresh time during startup
Key: SYNCOPE-1758
URL: https://issues.apache.org/jira/browse/SYNCOPE-1758
Project: Syncope
Issue Type: Improvement
Components: wa
Affects Versions: 3.0.3
Reporter: Fabio Martelli
Fix For: 3.0.4, 4.0.0
During startup the following exception is raised very often.
{code:java}
12:37:42.909 WARN org.apereo.cas.util.function.FunctionUtils -
NullPointerException
java.lang.NullPointerException: null
at
org.springframework.web.servlet.HttpServletBean$ServletConfigPropertyValues.(HttpServletBean.java:224)
~[spring-webmvc-5.3.22.jar!/:5.3.22]
at
org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:152)
~[spring-webmvc-5.3.22.jar!/:5.3.22]
at
org.apereo.cas.support.events.listener.DefaultCasConfigurationEventListener.lambda$initializeBeansEagerly$0(DefaultCasConfigurationEventListener.java:71)
~[cas-server-core-events-configuration-6.6.7.jar!/:6.6.7]
at
org.apereo.cas.util.function.FunctionUtils.doAndHandle(FunctionUtils.java:313)
~[cas-server-core-util-api-6.6.7.jar!/:6.6.7]
at
org.apereo.cas.support.events.listener.DefaultCasConfigurationEventListener.initializeBeansEagerly(DefaultCasConfigurationEventListener.java:64)
~[cas-server-core-events-configuration-6.6.7.jar!/:6.6.7]
at
org.apereo.cas.support.events.listener.DefaultCasConfigurationEventListener.onRefreshScopeRefreshed(DefaultCasConfigurationEventListener.java:48)
~[cas-server-core-events-configuration-6.6.7.jar!/:6.6.7]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
~[?:?]
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
~[?:?]
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
~[spring-aop-5.3.22.jar!/:5.3.22]
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
~[spring-aop-5.3.22.jar!/:5.3.22]
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
~[spring-aop-5.3.22.jar!/:5.3.22]
at
org.springframework.aop.interceptor.AsyncExecutionInterceptor.lambda$invoke$0(AsyncExecutionInterceptor.java:115)
~[spring-aop-5.3.22.jar!/:5.3.22]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
~[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
~[?:?]
at java.lang.Thread.run(Thread.java:829) ~[?:?]
12:37:42.909 WARN org.apereo.cas.util.function.FunctionUtils -
NullPointerException
java.lang.NullPointerException: null
at
org.springframework.web.servlet.HttpServletBean$ServletConfigPropertyValues.(HttpServletBean.java:224)
~[spring-webmvc-5.3.22.jar!/:5.3.22]
at
org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:152)
~[spring-webmvc-5.3.22.jar!/:5.3.22]
at
org.apereo.cas.support.events.listener.DefaultCasConfigurationEventListener.lambda$initializeBeansEagerly$0(DefaultCasConfigurationEventListener.java:71)
~[cas-server-core-events-configuration-6.6.7.jar!/:6.6.7]
at
org.apereo.cas.util.function.FunctionUtils.doAndHandle(FunctionUtils.java:313)
~[cas-server-core-util-api-6.6.7.jar!/:6.6.7]
at
org.apereo.cas.support.events.listener.DefaultCasConfigurationEventListener.initializeBeansEagerly(DefaultCasConfigurationEventListener.java:64)
~[cas-server-core-events-configuration-6.6.7.jar!/:6.6.7]
at
org.apereo.cas.support.events.listener.DefaultCasConfigurationEventListener.rebind(DefaultCasConfigurationEventListener.java:84)
~[cas-server-core-events-configuration-6.6.7.jar!/:6.6.7]
at
org.apereo.cas.support.events.listener.DefaultCasConfigurationEventListener.onEnvironmentChangedEvent(DefaultCasConfigurationEventListener.java:42)
~[cas-server-core-events-configuration-6.6.7.jar!/:6.6.7]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
~[?:?]
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
~[?:?]
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
~[spring-aop-5.3.22.jar!/:5.3.22
Re: [VOTE] Apache Syncope 3.0.3
+1 regards On Fri, May 5, 2023 at 11:22 AM Francesco Chicchiriccò wrote: > I've created a 3.0.3 release, with the following artifacts up for a vote: > > Please note that GIT links are not from gitbox.apache.org as usual, but > from GitHub mirror due to current incident > https://status.apache.org/incidents/y1t4w1bx0bc9 > > GIT source tag (7350b35933): > https://github.com/apache/syncope/releases/tag/syncope-3.0.3 > > List of changes: > https://github.com/apache/syncope/blob/syncope-3.0.3/CHANGES > > Staging artifacts: > https://dist.apache.org/repos/dist/dev/syncope/3.0.3/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachesyncope-1081/ > > Staging site: > https://syncope.apache.org/3.0.3/index.html > > PGP release keys (signed using 273DF287): > http://www.apache.org/dist/syncope/KEYS > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my +1 > Regards. > > -- > 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/ > >
Re: [VOTE] Apache Syncope 2.1.14
+1 regards On Fri, May 5, 2023 at 4:29 PM Francesco Chicchiriccò wrote: > I've created a 2.1.14 release, with the following artifacts up for a vote: > > Please note that GIT links are not from gitbox.apache.org as usual, but > from GitHub mirror due to current incident > https://status.apache.org/incidents/y1t4w1bx0bc9 > > GIT source tag (2bc40ed425): > https://github.com/apache/syncope/releases/tag/syncope-2.1.14 > > List of changes: > https://github.com/apache/syncope/blob/syncope-2.1.14/CHANGES > > Staging artifacts: > https://dist.apache.org/repos/dist/dev/syncope/2.1.14/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachesyncope-1082/ > > Staging site (not a typo, it is the same as for 3.0.3 being under vote): > https://syncope.apache.org/3.0.3/index.html > > PGP release keys (signed using 273DF287): > http://www.apache.org/dist/syncope/KEYS > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my +1 > Regards. > > -- > 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] [Created] (SYNCOPE-1757) Misalignment between SyncTokenSerializer and SyncTokenDeserializer in case of token given as a clear string
Fabio Martelli created SYNCOPE-1757:
---
Summary: Misalignment between SyncTokenSerializer and
SyncTokenDeserializer in case of token given as a clear string
Key: SYNCOPE-1757
URL: https://issues.apache.org/jira/browse/SYNCOPE-1757
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 3.0.3
Reporter: Fabio Martelli
Fix For: 3.0.4
If resource connector provides a syncToken as a clear string and if this string
is Base64 deserializable (i.e.AD uSNChanged "1934664") than serialization
works fine ("syncToken":"\{\"value\":\"1934664\"}") but deserialization needed
to ask for a new incremental PULL. In fact in this case the value is
deserialized as a byte array because deserialized Base64.
This behaviour cause the failure of the incremental PULL.
[https://github.com/apache/syncope/blob/3_0_X/core/provisioning-api/src/main/java/org/apache/syncope/core/provisioning/api/serialization/SyncTokenDeserializer.java]
[https://github.com/apache/syncope/blob/3_0_X/core/provisioning-api/src/main/java/org/apache/syncope/core/provisioning/api/serialization/SyncTokenSerializer.java]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SYNCOPE-1755) NullPointer exception during PULL delete operation in case of NO_MATCH
Fabio Martelli created SYNCOPE-1755: --- Summary: NullPointer exception during PULL delete operation in case of NO_MATCH Key: SYNCOPE-1755 URL: https://issues.apache.org/jira/browse/SYNCOPE-1755 Project: Syncope Issue Type: Bug Components: core Affects Versions: 3.0.3 Reporter: Fabio Martelli Assignee: Fabio Martelli Fix For: 2.1.14, 3.0.4, 4.0.0 During PULL, occurrence of a DELETE operation generates a NullPointer exception in case of NO_MATCH. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1753) Extend changes' history management to most relevant WA configuration objects
Fabio Martelli created SYNCOPE-1753: --- Summary: Extend changes' history management to most relevant WA configuration objects Key: SYNCOPE-1753 URL: https://issues.apache.org/jira/browse/SYNCOPE-1753 Project: Syncope Issue Type: Improvement Components: client, console, core Affects Versions: 3.0.2 Reporter: Fabio Martelli Assignee: Fabio Martelli Fix For: 3.0.3 Extend changes' history management to most relevant WA configuration objects -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1743) Add support for Ticket Expiration Policies into ClientApp
[ https://issues.apache.org/jira/browse/SYNCOPE-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabio Martelli updated SYNCOPE-1743: Summary: Add support for Ticket Expiration Policies into ClientApp (was: Add support for serviceTicketExpirationPolicy into ClientApp) > Add support for Ticket Expiration Policies into ClientApp > - > > Key: SYNCOPE-1743 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1743 > Project: Syncope > Issue Type: Improvement > Components: wa >Affects Versions: 3.0.2 > Reporter: Fabio Martelli >Priority: Minor > Fix For: 3.0.3, 4.0.0 > > > Add support for a further policies to be linked to a ClientApp: > ticketGrantingTicketExpirationPolicy, serviceTicketExpirationPolicy, > proxyTicketExpirationPolicy, proxyGrantingTicketExpirationPolicy, > > [https://apereo.github.io/cas/6.6.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service] > [https://apereo.github.io/cas/6.6.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service-1] > [https://apereo.github.io/cas/6.6.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service-2] > [https://apereo.github.io/cas/6.6.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service-3] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1743) Add support for serviceTicketExpirationPolicy into ClientApp
[ https://issues.apache.org/jira/browse/SYNCOPE-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabio Martelli updated SYNCOPE-1743: Description: Add support for a further policies to be linked to a ClientApp: ticketGrantingTicketExpirationPolicy, serviceTicketExpirationPolicy, proxyTicketExpirationPolicy, proxyGrantingTicketExpirationPolicy, [https://apereo.github.io/cas/6.6.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service] [https://apereo.github.io/cas/6.6.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service-1] [https://apereo.github.io/cas/6.6.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service-2] [https://apereo.github.io/cas/6.6.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service-3] was: Add support for a further policy to be lined to a ClientApp: serviceTicketExpirationPolicy. https://apereo.github.io/cas/6.6.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service > Add support for serviceTicketExpirationPolicy into ClientApp > > > Key: SYNCOPE-1743 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1743 > Project: Syncope > Issue Type: Improvement > Components: wa >Affects Versions: 3.0.2 > Reporter: Fabio Martelli >Priority: Minor > Fix For: 3.0.3, 4.0.0 > > > Add support for a further policies to be linked to a ClientApp: > ticketGrantingTicketExpirationPolicy, serviceTicketExpirationPolicy, > proxyTicketExpirationPolicy, proxyGrantingTicketExpirationPolicy, > > [https://apereo.github.io/cas/6.6.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service] > [https://apereo.github.io/cas/6.6.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service-1] > [https://apereo.github.io/cas/6.6.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service-2] > [https://apereo.github.io/cas/6.6.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service-3] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1743) Add support for serviceTicketExpirationPolicy into ClientApp
Fabio Martelli created SYNCOPE-1743: --- Summary: Add support for serviceTicketExpirationPolicy into ClientApp Key: SYNCOPE-1743 URL: https://issues.apache.org/jira/browse/SYNCOPE-1743 Project: Syncope Issue Type: Improvement Components: wa Affects Versions: 3.0.2 Reporter: Fabio Martelli Fix For: 3.0.3 Add support for a further policy to be lined to a ClientApp: serviceTicketExpirationPolicy. https://apereo.github.io/cas/6.6.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1741) Add support form Azure Active Directory delegated authentication
[ https://issues.apache.org/jira/browse/SYNCOPE-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabio Martelli resolved SYNCOPE-1741. - Resolution: Fixed > Add support form Azure Active Directory delegated authentication > > > Key: SYNCOPE-1741 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1741 > Project: Syncope > Issue Type: New Feature > Components: wa >Affects Versions: 3.0.2 > Reporter: Fabio Martelli > Assignee: Fabio Martelli >Priority: Minor > Fix For: 3.0.3 > > > Add support for > https://apereo.github.io/cas/6.6.x/integration/Delegate-Authentication-Azure-AD.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1741) Add support form Azure Active Directory delegated authentication
Fabio Martelli created SYNCOPE-1741: --- Summary: Add support form Azure Active Directory delegated authentication Key: SYNCOPE-1741 URL: https://issues.apache.org/jira/browse/SYNCOPE-1741 Project: Syncope Issue Type: New Feature Components: wa Affects Versions: 3.0.2 Reporter: Fabio Martelli Assignee: Fabio Martelli Fix For: 3.0.3 Add support for https://apereo.github.io/cas/6.6.x/integration/Delegate-Authentication-Azure-AD.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] Apache Syncope 3.0.2
+1 regards On Fri, Feb 17, 2023 at 11:08 AM Francesco Chicchiriccò wrote: > > I've created a 3.0.2 release, with the following artifacts up for a vote: > > GIT source tag (182c219da9): > https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=182c219da9 > > List of changes: > https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob_plain;f=CHANGES;hb=182c219da9 > > Staging artifacts: > https://dist.apache.org/repos/dist/dev/syncope/3.0.2/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachesyncope-1079/ > > Staging site: > https://syncope.apache.org/3.0.2/index.html > > PGP release keys (signed using 273DF287): > http://www.apache.org/dist/syncope/KEYS > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my +1 > Regards. > > -- > 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/ >
Re: [VOTE] Apache Syncope 3.0.1
+1 Reagrds On Fri, Jan 13, 2023 at 8:32 AM Francesco Chicchiriccò wrote: > > I've created a 3.0.1 release, with the following artifacts up for a vote: > > GIT source tag (e1d0c5b32d): > https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=e1d0c5b32d > > List of changes: > https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob_plain;f=CHANGES;hb=e1d0c5b32d > > Staging artifacts: > https://dist.apache.org/repos/dist/dev/syncope/3.0.1/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachesyncope-1076/ > > Staging site: > https://syncope.apache.org/3.0.1/index.html > > PGP release keys (signed using 273DF287): > http://www.apache.org/dist/syncope/KEYS > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my +1 > Regards. > > -- > 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/ >
Re: [VOTE] Apache Syncope 2.1.13
+1 Regards On Fri, Dec 9, 2022 at 10:56 AM Francesco Chicchiriccò wrote: > > I've created a 2.1.13 release, with the following artifacts up for a vote: > > GIT source tag (2d7958221b): > https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=2d7958221b > > List of changes: > https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob_plain;f=CHANGES;hb=2d7958221b > > Staging artifacts: > https://dist.apache.org/repos/dist/dev/syncope/2.1.13/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachesyncope-1075/ > > Staging site: > https://syncope.apache.org/2.1.13/index.html > > PGP release keys (signed using 273DF287): > http://www.apache.org/dist/syncope/KEYS > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my +1 > Regards. > > -- > 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/ >
Re: [VOTE] Apache Syncope 3.0.0-M2
+1 Regards On Thu, Oct 27, 2022 at 3:41 PM Francesco Chicchiriccò wrote: > > I've created a 3.0-0-M2 release, with the following artifacts up for a vote: > > GIT source tag (690dbfcaab): > https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=690dbfcaab > > List of changes: > https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob_plain;f=CHANGES;hb=690dbfcaab > > Staging artifacts: > https://dist.apache.org/repos/dist/dev/syncope/3.0.0-M2/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachesyncope-1073/ > > Staging site: > https://syncope.apache.org/3.0.0-M2/index.html > > PGP release keys (signed using 273DF287): > http://www.apache.org/dist/syncope/KEYS > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my +1 > Regards. > > -- > 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/ >
Re: [VOTE] Apache Syncope 3.0.0-M1
+1 Regards On Fri, Oct 14, 2022 at 9:16 AM Francesco Chicchiriccò wrote: > > I've created a 3.0-0-M1 release, with the following artifacts up for a vote: > > GIT source tag (680fc58faf): > https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=680fc58faf > > List of changes: > https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob_plain;f=CHANGES;hb=680fc58faf > > Staging artifacts: > https://dist.apache.org/repos/dist/dev/syncope/3.0.0-M1/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachesyncope-1072/ > > Staging site: > https://syncope.apache.org/3.0.0-M1/index.html > > PGP release keys (signed using 273DF287): > http://www.apache.org/dist/syncope/KEYS > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my +1 > Regards. > > -- > 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/ >
Re: [DISCUSS] Remove Camel Provisioning Manager
Hi Francesco, I completely agree with you. I do think we should keep the entire project as simple as possible. So, removing unused and quite useless extensions could be the right approach. Regards, F. On Wed, Aug 24, 2022 at 1:16 PM Francesco Chicchiriccò wrote: > > Hi all, > working for SYNCOPE-1692, which involves some changes in the provisioning > process, I've realized that the Camel Provisioning Manager extension [1], > while featuring some very smart code has probably never been used in any > production deployment, at least none that I am aware of. > > Over time, the cost of managing such (possibly unused) extension has become > quite relevant, hence I am proposing to remove it from the master branch, so > that next 3.0.0 release will not contain it anymore. > > Thoughts? > Regards. > > [1] https://github.com/apache/syncope/tree/master/ext/camel > > -- > 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/ >
Re: [VOTE] Apache Syncope 2.1.11
+1 Regards On Fri, Mar 18, 2022 at 10:30 AM Francesco Chicchiriccò wrote: > > I've created a 2.1.11 release, with the following artifacts up for a vote: > > GIT source tag (326c221): > https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=326c221 > > List of changes: > https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;hb=326c221 > > Staging artifacts: > https://dist.apache.org/repos/dist/dev/syncope/2.1.11/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachesyncope-1069/ > > Staging site: > http://syncope.apache.org/2.1.11/index.html > > PGP release keys (signed using 273DF287): > http://www.apache.org/dist/syncope/KEYS > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my +1 > Regards. > > -- > 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/ >
Re: [VOTE] Apache Syncope 2.1.10
Il 08/10/21 09:47, Francesco Chicchiriccò ha scritto: I've created a 2.1.10 release, with the following artifacts up for a vote: GIT source tag (d47a976): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=0761b43 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;hb=0761b43 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.10/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1068/ Staging site: http://syncope.apache.org/2.1.10/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. +1 Regards, F. -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
Re: [VOTE] Apache Syncope 2.1.9
Il 07/04/21 09:24, Francesco Chicchiriccò ha scritto: I've created a 2.1.9 release, with the following artifacts up for a vote: GIT source tag (d47a976): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=d47a976 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;hb=d47a976 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.9/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1067/ Staging site: http://syncope.apache.org/2.1.8/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. +1 Regards -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
[jira] [Created] (SYNCOPE-1609) Reduce the number of table joins into PostgreSQL JSONB persistence implementation
Fabio Martelli created SYNCOPE-1609: --- Summary: Reduce the number of table joins into PostgreSQL JSONB persistence implementation Key: SYNCOPE-1609 URL: https://issues.apache.org/jira/browse/SYNCOPE-1609 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 2.1.8 Reporter: Fabio Martelli Fix For: 2.1.9 By exploiting new JSON Functions and Operators provided with PostgreSQL 12 it would be possible to remove several useless joins in order to improve user and any object search performance. Take a look at "*JSON Processing Functions*" into [1]. [1]https://www.postgresql.org/docs/12/functions-json.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [VOTE] Apache Syncope 2.1.8
+1 Regards Il 18/12/20 09:46, Francesco Chicchiriccò ha scritto: I've created a 2.1.8 release, with the following artifacts up for a vote: GIT source tag (29738bc13cfbb7b26829c2b1bfb7df9649349984): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=800f7ea List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;hb=800f7ea Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.8/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1066/ Staging site: http://syncope.apache.org/2.1.8/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
Re: Rolling new release: 2.1.8
Il 17/12/20 12:15, Francesco Chicchiriccò ha scritto: Hi all, given the fact that we have some important fixes available for 2.1.8 [1], I would like to start soon the release process, with purpose of delivering a nice Christmas present to our users. Do you see any problem? Please go on. Thank you! Regards. [1] https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20done%20AND%20project%20%3D%2012313120%20AND%20fixVersion%20%3D%2012348788%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
Re: [VOTE] Apache Syncope 2.1.7
Il 11/09/20 11:37, Francesco Chicchiriccò ha scritto: I've created a 2.1.7 release, with the following artifacts up for a vote: GIT source tag (29738bc13cfbb7b26829c2b1bfb7df9649349984): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=29738bc13cfbb7b26829c2b1bfb7df9649349984 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;hb=29738bc13cfbb7b26829c2b1bfb7df9649349984 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.7/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1064/ Staging site: http://syncope.apache.org/2.1.7/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. +1 Regards -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
Re: [VOTE] Apache Syncope 2.0.15
Il 29/04/20 14:08, Francesco Chicchiriccò ha scritto: I've created a 2.0.15 release, with the following artifacts up for a vote: GIT source tag (2c668d5): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=2c668d5 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=a09206954f5db6800555b7c2932f229026d926d4;hb=2c668d5 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.0.15/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1063/ Staging site (yes, same as for 2.1.6, not a typo): http://syncope.apache.org/2.1.6/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. +1 Regards -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
Re: [VOTE] Apache Syncope 2.1.6
Il 29/04/20 14:00, Francesco Chicchiriccò ha scritto: I've created a 2.1.6 release, with the following artifacts up for a vote: GIT source tag (95f09c0): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=95f09c0 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=3b84fab4fff0fa4c49ba9c30c5ee9530788c2249;hb=95f09c0 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.6/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1062/ Staging site: http://syncope.apache.org/2.1.6/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. +1 Regards -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
[jira] [Updated] (SYNCOPE-1554) Generated default admin role layout doesn't work
[ https://issues.apache.org/jira/browse/SYNCOPE-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabio Martelli updated SYNCOPE-1554: Description: Steps to reproduce on the online syncope-vm: # create a role including all entitlements # provide a default layout for it # create a user with the role just created # login with the new user # click on Users from dashboard At this point an exception will occur (see below for the raised cause). Last cause: Unrecognized field "PRINTER" (class org.apache.syncope.client.console.layout.AnyLayout), not marked as ignorable (3 known properties: "anyPanelClass", "USER", "GROUP"]) was: Steps to reproduce on the online syncope-vm: # create a role including all entitlements # provide a default layout for it # create a user with the role just created # login with the new user # click on Users from dashboard At this point an exception will occur (see below for the raised cause). Last cause: Unrecognized field "PRINTER" (class org.apache.syncope.client.console.layout.AnyLayout), not marked as ignorable (3 known properties: "anyPanelClass", "USER", "GROUP"]) > Generated default admin role layout doesn't work > > > Key: SYNCOPE-1554 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1554 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.1.5 >Reporter: Fabio Martelli >Priority: Major > Fix For: 2.1.6, 3.0.0 > > > Steps to reproduce on the online syncope-vm: > # create a role including all entitlements > # provide a default layout for it > # create a user with the role just created > # login with the new user > # click on Users from dashboard > At this point an exception will occur (see below for the raised cause). > Last cause: Unrecognized field "PRINTER" (class > org.apache.syncope.client.console.layout.AnyLayout), not marked as ignorable > (3 known properties: "anyPanelClass", "USER", "GROUP"]) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1554) Generated default admin role layout doesn't work
Fabio Martelli created SYNCOPE-1554: --- Summary: Generated default admin role layout doesn't work Key: SYNCOPE-1554 URL: https://issues.apache.org/jira/browse/SYNCOPE-1554 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.1.5 Reporter: Fabio Martelli Fix For: 2.1.6, 3.0.0 Steps to reproduce on the online syncope-vm: # create a role including all entitlements # provide a default layout for it # create a user with the role just created # login with the new user # click on Users from dashboard At this point an exception will occur (see below for the raised cause). Last cause: Unrecognized field "PRINTER" (class org.apache.syncope.client.console.layout.AnyLayout), not marked as ignorable (3 known properties: "anyPanelClass", "USER", "GROUP"]) -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Time to cut 2.1.6 / 2.0.15?
Il 14/04/20 11:58, Francesco Chicchiriccò ha scritto: Hi there, I think it's about time to start preparing Syncope 2.1.6 / 2.0.15 (several fixes and improvement, time passed since previous releases, ..). If you have any pending change or fix, please either finalize as soon as possible or let's postpone. WDYT? Hi Francesco. No pending change/fix from my side. +1 to go on with the releases. Kind regards, F. -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
Re: Automating Syncope's dependency updates
Il 11/12/19 15:00, Misagh Moayyed ha scritto: Hey Team, I suspect most know about this sort of thing, but I thought to share this with you: https://github.com/renovatebot/renovate Wow, it is really widely used. Sounds really interesting to have it on Syncope. +1 for me I think this is a useful tool to allow a Github project such as Syncope to automatically receive dependency updates and become self sufficient. It will attempt to parse the project's dependencies/pom and will then begin to issue pull requests with relevant updates. Its schedule, update policy and inclusion/exclusion rules can all be controlled via a .renovate JSON file. It can run in two ways: 1- As a GitHub app, which would be installed for the Apache org on Github and enabled for select repositories, such as Syncope. This option requires coordination/permission from Apache infra, and updates are then automatic. 2- As a CLI tool, where a committer's personal access token is passed as a command-line argument, and the tool can run as part of CI. This option probably does not require anything from Apache infra [?], and updates can be cancelled as part of the CI job that runs the tool. I am not sure what the CLA policy would be for bots; the second option probably [?] covers this, as PRs are issued on behalf of the committer whose AT is used. Either way, it seems like we need clarification from Apache infra. This is an example of a pull request by the bot: https://github.com/Jasig/uPortal/pull/1849 This is an example of the bot's JSON configuration file: https://github.com/Jasig/uPortal/blob/master/renovate.json How do you feel about this? Is this a good option to pursue and follow up? The bot also has the ability to rebase PRs, and can also take over the merging process automatically if CI passes or other rules allow. (At some point in the future, I think it will also gain the ability to travel back in time and kill Sarah Connor [1], but that has yet to be fully verified.) --Misagh [1] https://www.wikiwand.com/en/Sarah_Connor_(Terminator) -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
[jira] [Commented] (SYNCOPE-957) Multiaccount
[ https://issues.apache.org/jira/browse/SYNCOPE-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986795#comment-16986795 ] Fabio Martelli commented on SYNCOPE-957: Pull report update missing as well: in case of create or update of new accounts no report info is provided > Multiaccount > > > Key: SYNCOPE-957 > URL: https://issues.apache.org/jira/browse/SYNCOPE-957 > Project: Syncope > Issue Type: New Feature >Reporter: Francesco Chicchiriccò >Assignee: Matteo Alessandroni >Priority: Major > Fix For: 2.1.6, 3.0.0 > > > Users, as groups and any objects, can be mapped to external resources and > pull, push or propagation might result in associating them to accounts there. > So far, there have always been a 1-to-1 correspondence between Syncope users > and external accounts, given a certain mapping for an external resource. > There are use cases, however, when this could be limiting: in particular, the > existence of "service accounts" which can be defined on LDAP or Active > Directory. In such cases, there could be more accounts mapping to a Syncope > user. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCUSS] Remove deb packages for Syncope 3.'0
+1 Regards Il sab 14 set 2019, 07:01 Francesco Chicchiriccò ha scritto: > Hi all, > I would like to propose to remove the deb packages from master branch / > 3.0, for some reasons: > > 1. it's difficult to produce packages compatible at the same time with > Debian, Ubuntu and other derivatives: for example, ATM Debian stable has a > tomcat9 package while Ubuntu LTS is still on tomcat8 > > 2. in branches 2_0_X and 2_1_X deb packages are used to build Docker > images but on master this has changed: since all is now based on Spring > Boot, Docker images were changed as consequence > > 3. there are new components on master (SRA, Keymaster, WA, .. [1]) that > would deserve new deb packages, but I don't think the effort is worthwhile, > especially given the reason above > > 4. deb packages were originally meant as a fast and straightforward way to > get Syncope properly deployed, but I think that nowadays Docker images > (with Docker Compose and Kubernetes samples) serve better such purpose, on > more platforms > > If there are no objections, I'll proceed with removal next week. > > Regards. > > [1] > https://cwiki.apache.org/confluence/display/SYNCOPE/%5BDISCUSS%5D+Syncope+3.0 > > -- > 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/ > >
Re: [VOTE] Apache Syncope 2.1.5
Il 12/09/19 10:56, Francesco Chicchiriccò ha scritto: I've created a 2.1.5 release, with the following artifacts up for a vote: GIT source tag (51e08a2): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=51e08a2 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=3b84fab4fff0fa4c49ba9c30c5ee9530788c2249;hb=51e08a2 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.5/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1060/ Staging site: http://syncope.apache.org/2.1.5/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. +1 Regards -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
Re: Plan to release 2.0.14 / 2.1.5 soon
Il 11/09/19 17:43, Francesco Chicchiriccò ha scritto: Hi there, since we have already 16 issues done for 2.0.14 [1] and 21 for 2.1.5 [2], I'd propose to postpone the remaining to later versions and to start the release process [3] for both in the next days. Any objection / showstopper ? Regards. [1] https://issues.apache.org/jira/projects/SYNCOPE/versions/12345389 [2] https://issues.apache.org/jira/projects/SYNCOPE/versions/12345390 [3] http://syncope.apache.org/release-process +1 I completely agree with the proposed plan. Regards, F. -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
[jira] [Created] (SYNCOPE-1485) Reindex of elasticsearch ends with memory error in case of a uge amount of data
fabio martelli created SYNCOPE-1485:
---
Summary: Reindex of elasticsearch ends with memory error in case
of a uge amount of data
Key: SYNCOPE-1485
URL: https://issues.apache.org/jira/browse/SYNCOPE-1485
Project: Syncope
Issue Type: Bug
Components: core, extensions
Affects Versions: 2.1.4, 2.0.13
Reporter: fabio martelli
Fix For: 2.0.14, 2.1.5, 3.0.0
In case of a huge amount of data, elastic search reindex ends with memory error.
See below an extract of the stacktrace.
12:28:21.014 ERROR
org.apache.syncope.core.provisioning.api.job.SchedTaskJobDelegate - While
executing task 0dfe540f-67aa-41a1-be54-0f67aa71a1f7
org.quartz.JobExecutionException: While rebuilding index for domain Master
at
org.apache.syncope.core.provisioning.java.job.ElasticsearchReindex.doExecute(ElasticsearchReindex.java:124)
~[syncope-ext-elasticsearch-provisioning-java-2.1.4.jar:2.1.4]
at
org.apache.syncope.core.provisioning.java.job.AbstractSchedTaskJobDelegate.execute(AbstractSchedTaskJobDelegate.java:122)
~[syncope-core-provisioning-java-2.1.4.jar:2.1.4]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_212]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
~[?:1.8.0_212]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:1.8.0_212]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_212]
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:343)
~[spring-aop-5.1.6.RELEASE.jar:5.1.6.RELEASE]
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
~[spring-aop-5.1.6.RELEASE.jar:5.1.6.RELEASE]
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
~[spring-aop-5.1.6.RELEASE.jar:5.1.6.RELEASE]
at
org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:294)
~[spring-tx-5.1.6.RELEASE.jar:5.1.6.RELEASE]
at
org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:98)
~[spring-tx-5.1.6.RELEASE.jar:5.1.6.RELEASE]
at
org.apache.syncope.core.persistence.jpa.spring.DomainTransactionInterceptor.invoke(DomainTransactionInterceptor.java:60)
~[syncope-core-persistence-jpa-2.1.4.jar:2.1.4]
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
~[spring-aop-5.1.6.RELEASE.jar:5.1.6.RELEASE]
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)
~[spring-aop-5.1.6.RELEASE.jar:5.1.6.RELEASE]
at com.sun.proxy.$Proxy355.execute(Unknown Source) ~[?:?]
at
org.apache.syncope.core.provisioning.java.job.TaskJob.lambda$execute$0(TaskJob.java:87)
~[syncope-core-provisioning-java-2.1.4.jar:2.1.4]
at
org.apache.syncope.core.spring.security.AuthContextUtils.execWithAuthContext(AuthContextUtils.java:117)
~[syncope-core-spring-2.1.4.jar:2.1.4]
at
org.apache.syncope.core.provisioning.java.job.TaskJob.execute(TaskJob.java:76)
~[syncope-core-provisioning-java-2.1.4.jar:2.1.4]
at org.quartz.core.JobRunShell.run(JobRunShell.java:202) ~[quartz-2.3.1.jar:?]
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
~[quartz-2.3.1.jar:?]
Caused by: org.apache.openjpa.persistence.PersistenceException: Ran out of
memory retrieving query results. {prepstmnt 1711473022 SELECT t0.id, t2.id,
t2.ACCOUNTPOLICY_ID, t3.id, t4.id, t4.ACCOUNTPOLICY_ID, t4.nam
e, t4.PARENT_ID, t4.PASSWORDPOLICY_ID, t3.bundleName, t3.connRequestTimeout,
t3.connectorName, t3.displayName, t3.jsonConf, t3.location, t3.maxIdle,
t3.maxObjects, t3.maxWait, t3.minEvictableIdleTimeMillis, t3.min
Idle, t3.version, t2.createTraceLevel, t2.deleteTraceLevel,
t2.enforceMandatoryCondition, t2.jsonConf, t2.overrideCapabilities,
t2.PASSWORDPOLICY_ID, t2.propagationPriority, t2.provisioningTraceLevel,
t2.PULLPOLIC
Y_ID, t2.PUSHPOLICY_ID, t2.randomPwdIfNotProvided, t2.updateTraceLevel FROM
SyncopeUser t0 INNER JOIN SyncopeUser_ExternalResource t1 ON t0.id = t1.user_id
INNER JOIN ExternalResource t2 ON t1.resource_id = t2.id
LEFT OUTER JOIN ConnInstance t3 ON t2.CONNECTOR_ID = t3.id LEFT OUTER JOIN
Realm t4 ON t3.ADMINREALM_ID = t4.id ORDER BY t0.id ASC} [code=0, state=53200]
at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:5250)
~[openjpa-jdbc-3.1.0.jar:3.1.0]
at
org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:5210)
~[openjpa-jdbc-3.1.0.jar:3.1.0]
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:134)
~[openjpa-jdbc-3.1.0.jar:3.1.0]
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:115)
~[openjpa-jdbc-3.1.0.jar:3.1.0
Re: [VOTE] Apache Syncope 2.0.13
Il 19/04/19 11:53, Francesco Chicchiriccò ha scritto: I've created a 2.0.13 release, with the following artifacts up for a vote: GIT source tag (3dc84c4): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=3dc84c4 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=87754582fba4d1ed082c784053b5ad921b5b7bdb;hb=3dc84c4 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.0.13/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1059/ Staging site (yes, same as for 2.1.4, not a typo): http://syncope.apache.org/2.1.4/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. +1 Regards -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
Re: [VOTE] Apache Syncope 2.1.4
Il 19/04/19 10:29, Francesco Chicchiriccò ha scritto: I've created a 2.1.4 release, with the following artifacts up for a vote: GIT source tag (0cd9070): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=0cd9070 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=dba9102ecf4561644c9c109cd06df30550891c2e;hb=0cd9070 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.4/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1058/ Staging site: http://syncope.apache.org/2.1.4/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. +1 Regards -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
[jira] [Updated] (SYNCOPE-1439) User membership attributes not updated
[ https://issues.apache.org/jira/browse/SYNCOPE-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli updated SYNCOPE-1439: Affects Version/s: 2.0.12 Fix Version/s: 2.0.13 Same issue in case of create. Same issue for membership attributes not multivalue. > User membership attributes not updated > -- > > Key: SYNCOPE-1439 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1439 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.12, 2.1.3 >Reporter: Matteo Alessandroni >Assignee: Matteo Alessandroni >Priority: Major > Fix For: 2.0.13, 2.1.4, 3.0.0 > > > # Start from a clean Syncope (especially no derived and virtual attributes); > # Create a Plain Attribute and add it to an AnyTypeClass; > # Create a Type Extension for a Group to USER; > # Create a new user with plain attributes only, *set a value for the > specific membership attribute from the type extension* and save user; > # Edit the same user and change value to the same attribute (add or remove > all values if it's multivalue). > *Result*: changes on membership attribute are not saved. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1436) Remove pullPolicy EAGER fetchType from JPAExternalResource
[ https://issues.apache.org/jira/browse/SYNCOPE-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1436. - Resolution: Fixed > Remove pullPolicy EAGER fetchType from JPAExternalResource > -- > > Key: SYNCOPE-1436 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1436 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 2.0.12, 2.1.3 > Reporter: fabio martelli > Assignee: fabio martelli >Priority: Major > Fix For: 2.0.13, 2.1.4, 3.0.0 > > > Change pullPolicy fetch type to LAZY into JPAExternalResource -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1436) Remove pullPolicy EAGER fetchType from JPAExternalResource
fabio martelli created SYNCOPE-1436: --- Summary: Remove pullPolicy EAGER fetchType from JPAExternalResource Key: SYNCOPE-1436 URL: https://issues.apache.org/jira/browse/SYNCOPE-1436 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 2.1.3, 2.0.12 Reporter: fabio martelli Assignee: fabio martelli Fix For: 2.0.13, 2.1.4, 3.0.0 Change pullPolicy fetch type to LAZY into JPAExternalResource -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1433) Unflag/flag uniqueness shouldn't be permitted
[ https://issues.apache.org/jira/browse/SYNCOPE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1433. - Resolution: Fixed > Unflag/flag uniqueness shouldn't be permitted > - > > Key: SYNCOPE-1433 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1433 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.0.12, 2.1.3 > Reporter: fabio martelli > Assignee: fabio martelli >Priority: Major > Fix For: 2.0.13, 2.1.4, 3.0.0 > > > Console does not permit flag/unflag of uniqueness editing existing schemas -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1434) getRemoteObject into AbstractPropagationTaskExecutor does not check for null object before retrieving attribute from
[ https://issues.apache.org/jira/browse/SYNCOPE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1434. - Resolution: Fixed > getRemoteObject into AbstractPropagationTaskExecutor does not check for null > object before retrieving attribute from > > > Key: SYNCOPE-1434 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1434 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 2.0.12 > Reporter: fabio martelli >Assignee: fabio martelli >Priority: Major > Fix For: 2.0.13 > > > getRemoteObject into AbstractPropagationTaskExecutor does not check for null > object before retrieving attribute from -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1434) getRemoteObject into AbstractPropagationTaskExecutor does not check for null object before retrieving attribute from
fabio martelli created SYNCOPE-1434: --- Summary: getRemoteObject into AbstractPropagationTaskExecutor does not check for null object before retrieving attribute from Key: SYNCOPE-1434 URL: https://issues.apache.org/jira/browse/SYNCOPE-1434 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 2.0.12 Reporter: fabio martelli Assignee: fabio martelli Fix For: 2.0.13 getRemoteObject into AbstractPropagationTaskExecutor does not check for null object before retrieving attribute from -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1433) Unflag/flag uniqueness shouldn't be permitted
fabio martelli created SYNCOPE-1433: --- Summary: Unflag/flag uniqueness shouldn't be permitted Key: SYNCOPE-1433 URL: https://issues.apache.org/jira/browse/SYNCOPE-1433 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 2.1.3, 2.0.12 Reporter: fabio martelli Fix For: 2.0.13, 2.1.4, 3.0.0 Console does not permit flag/unflag of uniqueness editing existing schemas -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [VOTE] Apache Syncope 2.0.12
Il 17/01/19 17:39, Francesco Chicchiriccò ha scritto: I've created a 2.0.12 release, with the following artifacts up for a vote: GIT source tag (770e696): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=770e696 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=7babeeaef0ecc2f7a4da042fde9e387a035ceced;hb=770e696 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.0.12/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1057/ Staging site (yes, same as for 2.1.3, not a typo): http://syncope.apache.org/2.1.3/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. +1 regards -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
Re: [VOTE] Apache Syncope 2.1.3
Il 17/01/19 17:39, Francesco Chicchiriccò ha scritto: I've created a 2.1.3 release, with the following artifacts up for a vote: GIT source tag (5121355): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=5121355 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=7babeeaef0ecc2f7a4da042fde9e387a035ceced;hb=5121355 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.3/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1056/ Staging site: http://syncope.apache.org/2.1.3/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. +1 regards -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
[jira] [Resolved] (SYNCOPE-1424) Improve Propagation task ordered search
[ https://issues.apache.org/jira/browse/SYNCOPE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1424. - Resolution: Fixed > Improve Propagation task ordered search > --- > > Key: SYNCOPE-1424 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1424 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 2.0.11, 2.1.2 > Reporter: fabio martelli > Assignee: fabio martelli >Priority: Major > Fix For: 2.0.12, 2.1.3, 3.0.0 > > > Performance of propagation tasks ordered search are terrible. > Since sometimes this kind of query could result in timeout, it is pretty > important to try to improve the current solution -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1424) Improve Propagation task ordered search
fabio martelli created SYNCOPE-1424: --- Summary: Improve Propagation task ordered search Key: SYNCOPE-1424 URL: https://issues.apache.org/jira/browse/SYNCOPE-1424 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 2.1.2, 2.0.11 Reporter: fabio martelli Assignee: fabio martelli Fix For: 2.0.12, 2.1.3, 3.0.0 Performance of propagation tasks ordered search are terrible. Since sometimes this kind of query could result in timeout, it is pretty important to try to improve the current solution -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1422) Permit to provide custom implementation of NotificationManager and AuditManager
[ https://issues.apache.org/jira/browse/SYNCOPE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1422. - Resolution: Fixed > Permit to provide custom implementation of NotificationManager and > AuditManager > --- > > Key: SYNCOPE-1422 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1422 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 2.0.11, 2.1.2 > Reporter: fabio martelli >Assignee: fabio martelli >Priority: Minor > Fix For: 2.0.12, 2.1.3, 3.0.0 > > > Permit to specify custom implementation into provisioning.properties -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1422) Permit to provide custom implementation of NotificationManager and AuditManager
fabio martelli created SYNCOPE-1422: --- Summary: Permit to provide custom implementation of NotificationManager and AuditManager Key: SYNCOPE-1422 URL: https://issues.apache.org/jira/browse/SYNCOPE-1422 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 2.1.2, 2.0.11 Reporter: fabio martelli Assignee: fabio martelli Fix For: 2.0.12, 2.1.3, 3.0.0 Permit to specify custom implementation into provisioning.properties -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1419) User and AnyObject search fails in case of not leaf conditions given on multivalue fields
[ https://issues.apache.org/jira/browse/SYNCOPE-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1419. - Resolution: Fixed > User and AnyObject search fails in case of not leaf conditions given on > multivalue fields > - > > Key: SYNCOPE-1419 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1419 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.11, 2.1.2 > Reporter: fabio martelli >Assignee: fabio martelli >Priority: Major > Fix For: 2.0.12, 2.1.3, 3.0.0 > > > Not condition on multivalue fields are always true -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SYNCOPE-1419) User and AnyObject search fails in case of not leaf conditions given on multivalue fields
[ https://issues.apache.org/jira/browse/SYNCOPE-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli updated SYNCOPE-1419: Summary: User and AnyObject search fails in case of not leaf conditions given on multivalue fields (was: User and AnyObject searchs fail in case of not leaf conditions given on multivalue fields) > User and AnyObject search fails in case of not leaf conditions given on > multivalue fields > - > > Key: SYNCOPE-1419 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1419 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.11, 2.1.2 > Reporter: fabio martelli >Assignee: fabio martelli >Priority: Major > Fix For: 2.0.12, 2.1.3, 3.0.0 > > > Not condition on multivalue fields are always true -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1419) User and AnyObject searchs fail in case of not leaf conditions given on multivalue fields
fabio martelli created SYNCOPE-1419: --- Summary: User and AnyObject searchs fail in case of not leaf conditions given on multivalue fields Key: SYNCOPE-1419 URL: https://issues.apache.org/jira/browse/SYNCOPE-1419 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.1.2, 2.0.11 Reporter: fabio martelli Assignee: fabio martelli Fix For: 2.0.12, 2.1.3, 3.0.0 Not condition on multivalue fields are always true -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1416) remove user_search_null_attr view
[ https://issues.apache.org/jira/browse/SYNCOPE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1416. - Resolution: Fixed > remove user_search_null_attr view > - > > Key: SYNCOPE-1416 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1416 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 2.0.11, 2.1.2 > Reporter: fabio martelli > Assignee: fabio martelli >Priority: Major > Fix For: 2.0.12, 2.1.3, 3.0.0 > > > Remove user_search_null_attr view because affects performance negatively -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1416) remove user_search_null_attr view
fabio martelli created SYNCOPE-1416: --- Summary: remove user_search_null_attr view Key: SYNCOPE-1416 URL: https://issues.apache.org/jira/browse/SYNCOPE-1416 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 2.1.2, 2.0.11 Reporter: fabio martelli Assignee: fabio martelli Fix For: 2.0.12, 2.1.3, 3.0.0 Remove user_search_null_attr view because affects performance negatively -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (SYNCOPE-1411) User/Any object updates generate attributes with null owner in case of patches involving membership attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714715#comment-16714715 ] fabio martelli edited comment on SYNCOPE-1411 at 12/10/18 3:43 PM: --- Remove null attributes by using the following queries and restart. delete from uplainattrvalue where attribute_id in (select id from uplainattr where owner_id IS NULL) delete from uplainattr where owner_id IS NULL was (Author: fmartelli): Remove null attributes by using the following queries and restart. delete from uplainattruniquevalue where attribute_id in (select id from uplainattr where owner_id IS NULL) delete from uplainattr where owner_id IS NULL > User/Any object updates generate attributes with null owner in case of > patches involving membership attributes > -- > > Key: SYNCOPE-1411 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1411 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.11, 2.1.2 > Reporter: fabio martelli >Assignee: fabio martelli >Priority: Major > Fix For: 2.0.12, 2.1.3, 3.0.0 > > > It seems that JPA "cascade" is not working in case of identity patching > involving membership attributes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1411) User/Any object updates generate attributes with null owner in case of patches involving membership attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1411. - Resolution: Fixed > User/Any object updates generate attributes with null owner in case of > patches involving membership attributes > -- > > Key: SYNCOPE-1411 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1411 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.11, 2.1.2 > Reporter: fabio martelli >Assignee: fabio martelli >Priority: Major > Fix For: 2.0.12, 2.1.3, 3.0.0 > > > It seems that JPA "cascade" is not working in case of identity patching > involving membership attributes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1412) Serch for identities with null attributes can be improved
[ https://issues.apache.org/jira/browse/SYNCOPE-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1412. - Resolution: Fixed > Serch for identities with null attributes can be improved > -- > > Key: SYNCOPE-1412 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1412 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 2.0.11, 2.1.2 > Reporter: fabio martelli > Assignee: fabio martelli >Priority: Major > Fix For: 2.0.12, 2.1.3, 3.0.0 > > > anyObject_search_null_attr and user_search_null_attr views can affect the > performence of searches in several cases. Change into the corresponding > search DAO in order to try to avoid these views as much as possible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (SYNCOPE-1411) User/Any object updates generate attributes with null owner in case of patches involving membership attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714715#comment-16714715 ] fabio martelli edited comment on SYNCOPE-1411 at 12/10/18 1:23 PM: --- Remove null attributes by using the following queries and restart. delete from uplainattruniquevalue where attribute_id in (select id from uplainattr where owner_id IS NULL) delete from uplainattr where owner_id IS NULL was (Author: fmartelli): Remove null value by using the following queries. delete from uplainattruniquevalue where attribute_id in (select id from uplainattr where owner_id IS NULL) delete from uplainattr where owner_id IS NULL > User/Any object updates generate attributes with null owner in case of > patches involving membership attributes > -- > > Key: SYNCOPE-1411 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1411 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.11, 2.1.2 > Reporter: fabio martelli >Assignee: fabio martelli >Priority: Major > Fix For: 2.0.12, 2.1.3, 3.0.0 > > > It seems that JPA "cascade" is not working in case of identity patching > involving membership attributes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1411) User/Any object updates generate attributes with null owner in case of patches involving membership attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714715#comment-16714715 ] fabio martelli commented on SYNCOPE-1411: - Remove null value by using the following queries. delete from uplainattruniquevalue where attribute_id in (select id from uplainattr where owner_id IS NULL) delete from uplainattr where owner_id IS NULL > User/Any object updates generate attributes with null owner in case of > patches involving membership attributes > -- > > Key: SYNCOPE-1411 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1411 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.11, 2.1.2 > Reporter: fabio martelli >Assignee: fabio martelli >Priority: Major > Fix For: 2.0.12, 2.1.3, 3.0.0 > > > It seems that JPA "cascade" is not working in case of identity patching > involving membership attributes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1412) Serch for identities with null attributes can be improved
fabio martelli created SYNCOPE-1412: --- Summary: Serch for identities with null attributes can be improved Key: SYNCOPE-1412 URL: https://issues.apache.org/jira/browse/SYNCOPE-1412 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 2.1.2, 2.0.11 Reporter: fabio martelli Assignee: fabio martelli Fix For: 2.0.12, 2.1.3, 3.0.0 anyObject_search_null_attr and user_search_null_attr views can affect the performence of searches in several cases. Change into the corresponding search DAO in order to try to avoid these views as much as possible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1411) User/Any object updates generate attributes with null owner in case of patches involving membership attributes
fabio martelli created SYNCOPE-1411: --- Summary: User/Any object updates generate attributes with null owner in case of patches involving membership attributes Key: SYNCOPE-1411 URL: https://issues.apache.org/jira/browse/SYNCOPE-1411 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.1.2, 2.0.11 Reporter: fabio martelli Assignee: fabio martelli Fix For: 2.0.12, 2.1.3, 3.0.0 It seems that JPA "cascade" is not working in case of identity patching involving membership attributes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1396) Give the possibility to trust all certificates from syncope client
fabio martelli created SYNCOPE-1396: --- Summary: Give the possibility to trust all certificates from syncope client Key: SYNCOPE-1396 URL: https://issues.apache.org/jira/browse/SYNCOPE-1396 Project: Syncope Issue Type: Improvement Components: client Affects Versions: 2.1.2, 2.0.11 Reporter: fabio martelli Fix For: 2.0.12, 2.1.3, 3.0.0 Provide a new setter into SyncopeClientFactoryBean in order to be able to set a sort of trust all certs flag. Change into the factory is required in order to include the authentication in this behavior... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [VOTE] Apache Syncope 2.1.2
+1 Regards Il 2 novembre 2018 16:04:06 CET, "Francesco Chicchiriccò" ha scritto: >I've created a 2.1.2 release, with the following artifacts up for a >vote: > >GIT source tag (7ea54c302ea4847f0e4e9d2255305c864ee68b1c): >https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=7ea54c302ea4847f0e4e9d2255305c864ee68b1c > >List of changes: >https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=fd9ec50e83ea96c021c60092adcbf2019c006422;hb=7ea54c302ea4847f0e4e9d2255305c864ee68b1c > >Staging artifacts: >https://dist.apache.org/repos/dist/dev/syncope/2.1.2/ > >Maven staging repo: >https://repository.apache.org/content/repositories/orgapachesyncope-1054/ > >Staging site: >http://syncope.apache.org/2.1.2/index.html > >PGP release keys (signed using 273DF287): >http://www.apache.org/dist/syncope/KEYS > >Vote will be open for 72 hours. > >[ ] +1 approve >[ ] +0 no opinion >[ ] -1 disapprove (and reason why) > >Here's my +1 >Regards. > >-- >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/ -- Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevità.
Re: [VOTE] Apache Syncope 2.0.11
+1 Regards Il 2 novembre 2018 16:04:08 CET, "Francesco Chicchiriccò" ha scritto: >I've created a 2.0.11 release, with the following artifacts up for a >vote: > >GIT source tag (d8085b6a013754f589ada294db49129f464e07ef): >https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=d8085b6a013754f589ada294db49129f464e07ef > >List of changes: >https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=a018252663f769ad5f8f781e8ddfa2ec02f16a79;hb=d8085b6a013754f589ada294db49129f464e07ef > >Staging artifacts: >https://dist.apache.org/repos/dist/dev/syncope/2.0.11/ > >Maven staging repo: >https://repository.apache.org/content/repositories/orgapachesyncope-1055/ > >Staging site (yes, same as for 2.1.2, not a typo): >http://syncope.apache.org/2.1.2/index.html > >PGP release keys (signed using 273DF287): >http://www.apache.org/dist/syncope/KEYS > >Vote will be open for 72 hours. > >[ ] +1 approve >[ ] +0 no opinion >[ ] -1 disapprove (and reason why) > >Here's my +1 >Regards. > >-- >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/ -- Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevità.
Re: [DISCUSS] - gitbox migration / take 2
Hi Francesco. This sounds really good! +1 Regards, F. Il 25/10/18 13:57, Francesco Chicchiriccò ha scritto: Hi all, we briefly discussed this item about one year ago [1], when we did not found enough reasons to jump on that. Now that things seem to work quite well for several other projects [2], and that we have seen few PRs coming, I am reconsidering this possibility. WDYT? Regards. [1] https://lists.apache.org/thread.html/d28709231a99719a3bf26d37b857f05709b02ed89c1de9cbeeddd973@%3Cdev.syncope.apache.org%3E [2] https://gitbox.apache.org/repos/asf -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
[jira] [Resolved] (SYNCOPE-1389) In case of virtual attribute mapping, propagation is always set as UPDATE also in case of CREATE
[ https://issues.apache.org/jira/browse/SYNCOPE-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1389. - Resolution: Fixed > In case of virtual attribute mapping, propagation is always set as UPDATE > also in case of CREATE > > > Key: SYNCOPE-1389 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1389 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.10, 2.1.1 > Reporter: fabio martelli >Assignee: fabio martelli >Priority: Major > Fix For: 2.0.11, 2.1.2, 3.0.0 > > > Into PropagationManagerImpl, in case of virtual attribute mapping, > propagation is always set as UPDATE also in case of CREATE -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1389) In case of virtual attribute mapping, propagation is always set as UPDATE also in case of CREATE
fabio martelli created SYNCOPE-1389: --- Summary: In case of virtual attribute mapping, propagation is always set as UPDATE also in case of CREATE Key: SYNCOPE-1389 URL: https://issues.apache.org/jira/browse/SYNCOPE-1389 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.1.1, 2.0.10 Reporter: fabio martelli Assignee: fabio martelli Fix For: 2.0.11, 2.1.2, 3.0.0 Into PropagationManagerImpl, in case of virtual attribute mapping, propagation is always set as UPDATE also in case of CREATE -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1385) Priority propagation timeout hard coded into PriorityPropagationTaskExecutor
[ https://issues.apache.org/jira/browse/SYNCOPE-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1385. - Resolution: Fixed > Priority propagation timeout hard coded into PriorityPropagationTaskExecutor > > > Key: SYNCOPE-1385 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1385 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 2.0.10, 2.1.1 > Reporter: fabio martelli > Assignee: fabio martelli >Priority: Major > Fix For: 2.0.11, 2.1.2, 3.0.0 > > > Waiting timeout for priority propagation is hard coded into > PriorityPropagationTaskExecutor to 60 seconds. Since connectors can be > configured to provide connection timeouts, it would be nice to have a timeout > at least close to the maximum connection request timeout given for connectors. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1385) Priority propagation timeout hard coded into PriorityPropagationTaskExecutor
fabio martelli created SYNCOPE-1385: --- Summary: Priority propagation timeout hard coded into PriorityPropagationTaskExecutor Key: SYNCOPE-1385 URL: https://issues.apache.org/jira/browse/SYNCOPE-1385 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 2.1.1, 2.0.10 Reporter: fabio martelli Assignee: fabio martelli Fix For: 2.0.11, 2.1.2, 3.0.0 Waiting timeout for priority propagation is hard coded into PriorityPropagationTaskExecutor to 60 seconds. Since connectors can be configured to provide connection timeouts, it would be nice to have a timeout at least close to the maximum connection request timeout given for connectors. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1383) Exception during "getObject" from external resource
[ https://issues.apache.org/jira/browse/SYNCOPE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1383. - Resolution: Fixed > Exception during "getObject" from external resource > --- > > Key: SYNCOPE-1383 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1383 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.10, 2.1.1 >Reporter: fabio martelli >Assignee: fabio martelli >Priority: Major > Fix For: 2.0.11, 2.1.2, 3.0.0 > > > Exception is raised performing getObject from resource. > > 09:06:18.573 ERROR > org.apache.syncope.core.provisioning.java.ConnectorFacadeProxy - Connector > request execution failure > java.util.concurrent.ExecutionException: java.lang.ClassCastException: > org.apache.syncope.core.provisioning.java.AsyncConnectorFacade$1 cannot be > cast to org.identityconnectors.framework.spi.SearchResultsHandler > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > ~[?:1.8.0_141] > at java.util.concurrent.FutureTask.get(FutureTask.java:206) ~[?:1.8.0_141] > at > org.apache.syncope.core.provisioning.java.ConnectorFacadeProxy.getObject(ConnectorFacadeProxy.java:417) > ~[syncope-core-provisioning-java-2.0.10.jar:?] > at > org.apache.syncope.core.provisioning.java.propagation.AbstractPropagationTaskExecutor.getRemoteObject(AbstractPropagationTaskExecutor.java:641) > ~[syncope-core-provisioning-java-2.0.10.jar:2.0.10] > at > org.apache.syncope.core.provisioning.java.propagation.AbstractPropagationTaskExecutor.execute(AbstractPropagationTaskExecutor.java:421) > ~[syncope-core-provisioning-java-2.0.10.jar:2.0.10] > at > org.apache.syncope.core.provisioning.java.propagation.DefaultPropagationTaskCallable.call(DefaultPropagationTaskCallable.java:89) > ~[syncope-core-provisioning-java-2.0.10.jar:2.0.10] > at > org.apache.syncope.core.provisioning.java.propagation.DefaultPropagationTaskCallable.call(DefaultPropagationTaskCallable.java:38) > ~[syncope-core-provisioning-java-2.0.10.jar:2.0.10] > at sun.reflect.GeneratedMethodAccessor888.invoke(Unknown Source) ~[?:?] > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > ~[?:1.8.0_141] > at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_141] > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) > ~[spring-aop-4.3.18.RELEASE.jar:4.3.18.RELEASE] > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) > ~[spring-aop-4.3.18.RELEASE.jar:4.3.18.RELEASE] > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) > ~[spring-aop-4.3.18.RELEASE.jar:4.3.18.RELEASE] > at > org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99) > ~[spring-tx-4.3.18.RELEASE.jar:4.3.18.RELEASE] > at > org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:282) > ~[spring-tx-4.3.18.RELEASE.jar:4.3.18.RELEASE] > at > org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96) > ~[spring-tx-4.3.18.RELEASE.jar:4.3.18.RELEASE] > at > org.apache.syncope.core.persistence.jpa.spring.DomainTransactionInterceptor.invoke(DomainTransactionInterceptor.java:64) > ~[syncope-core-persistence-jpa-2.0.10.jar:2.0.10] > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) > ~[spring-aop-4.3.18.RELEASE.jar:4.3.18.RELEASE] > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213) > ~[spring-aop-4.3.18.RELEASE.jar:4.3.18.RELEASE] > at com.sun.proxy.$Proxy603.call(Unknown Source) ~[?:?] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_141] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ~[?:1.8.0_141] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_141] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > ~[?:1.8.0_141] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > ~[?:1.8.0_141] > at java.lang.Thread.run(Thread.java:748) [?:1.8.0_141] > Caused by: java.lang.C
[jira] [Resolved] (SYNCOPE-1382) Failure specifying push task filters including db column mapped as integer
[
https://issues.apache.org/jira/browse/SYNCOPE-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabio martelli resolved SYNCOPE-1382.
-
Resolution: Fixed
> Failure specifying push task filters including db column mapped as integer
> --
>
> Key: SYNCOPE-1382
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1382
> Project: Syncope
> Issue Type: Improvement
> Components: console
>Affects Versions: 2.0.10, 2.1.1
> Reporter: fabio martelli
> Assignee: fabio martelli
>Priority: Major
> Fix For: 2.0.11, 2.1.2, 3.0.0
>
>
> It seems that case insensitive approach is used for boolean fields mapped on
> integer columns.
> Failures are experienced with boolean on postgresql. See exception below.
> Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: ERROR: function
> lower(integer) does not exist
> Hint: No function matches the given name and argument types. You might need
> to add explicit type casts.
> Position: 132 \{prepstmnt 2084826893 SELECT COUNT(any_id) FROM (SELECT
> u.any_id FROM (SELECT DISTINCT any_id FROM anyObject_search_attr WHERE
> ((schema_id='enabled' AND LOWER (booleanvalue)=LOWER(?) AND any_id IN (
> SELECT DISTINCT any_id FROM anyObject_search_attr WHERE schema_id='enabled'
> AND LOWER (booleanvalue)=LOWER(?))) AND any_id IN ( SELECT DISTINCT any_id
> FROM anyObject_search WHERE type_id=?))) u WHERE u.any_id IN (SELECT any_id
> FROM anyObject_search WHERE realm_id IN (SELECT id AS realm_id FROM Realm
> WHERE id=? OR id=?))) count_any_id} [code=0, state=42883]
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:218)
> ~[openjpa-lib-2.4.3.jar:2.4.3]
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:202)
> ~[openjpa-lib-2.4.3.jar:2.4.3]
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:58)
> ~[openjpa-lib-2.4.3.jar:2.4.3]
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeQuery(LoggingConnectionDecorator.java:1117)
> ~[openjpa-lib-2.4.3.jar:2.4.3]
> at
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:268)
> ~[openjpa-lib-2.4.3.jar:2.4.3]
> at
> org.apache.openjpa.jdbc.sql.PostgresDictionary$PostgresPreparedStatement.executeQuery(PostgresDictionary.java:1011)
> ~[openjpa-jdbc-2.4.3.jar:2.4.3]
> at
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:268)
> ~[openjpa-lib-2.4.3.jar:2.4.3]
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeQuery(JDBCStoreManager.java:1800)
> ~[openjpa-jdbc-2.4.3.jar:2.4.3]
> at
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:258)
> ~[openjpa-lib-2.4.3.jar:2.4.3]
> at
> org.apache.openjpa.jdbc.kernel.SQLStoreQuery$SQLExecutor.executeQuery(SQLStoreQuery.java:317)
> ~[openjpa-jdbc-2.4.3.jar:2.4.3]
> at
> org.apache.openjpa.jdbc.kernel.SQLStoreQuery$SQLExecutor.executeQuery(SQLStoreQuery.java:220)
> ~[openjpa-jdbc-2.4.3.jar:2.4.3]
> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1011)
> ~[openjpa-kernel-2.4.3.jar:2.4.3]
> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:869)
> ~[openjpa-kernel-2.4.3.jar:2.4.3]
> at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:800)
> ~[openjpa-kernel-2.4.3.jar:2.4.3]
> at
> org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:541)
> ~[openjpa-kernel-2.4.3.jar:2.4.3]
> at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:274)
> ~[openjpa-persistence-2.4.3.jar:2.4.3]
> at
> org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:290)
> ~[openjpa-persistence-2.4.3.jar:2.4.3]
> at
> org.apache.openjpa.persistence.QueryImpl.getSingleResult(QueryImpl.java:318)
> ~[openjpa-persistence-2.4.3.jar:2.4.3]
> at
> org.apache.syncope.core.persistence.jpa.dao.JPAAnySearchDAO.doCount(JPAAnySearchDAO.java:143)
> ~[syncope-core-persistence-jpa-2.0.10.jar:2.0.10]
> at
> org.apache.syncope.core.persistence.jpa.dao.AbstractAnySearchDAO.count(AbstractAnySearchDAO.java:129)
> ~[syncope-core-persistence-jpa-2.0.10.jar:2.0.10]
> at
> org.apache.syncope.core.provisioning.java.pushpull.PushJobDelegate.doExec
[jira] [Created] (SYNCOPE-1383) Exception during "getObject" from external resource
fabio martelli created SYNCOPE-1383: --- Summary: Exception during "getObject" from external resource Key: SYNCOPE-1383 URL: https://issues.apache.org/jira/browse/SYNCOPE-1383 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.1.1, 2.0.10 Reporter: fabio martelli Assignee: fabio martelli Fix For: 2.0.11, 2.1.2, 3.0.0 Exception is raised performing getObject from resource. 09:06:18.573 ERROR org.apache.syncope.core.provisioning.java.ConnectorFacadeProxy - Connector request execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException: org.apache.syncope.core.provisioning.java.AsyncConnectorFacade$1 cannot be cast to org.identityconnectors.framework.spi.SearchResultsHandler at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:1.8.0_141] at java.util.concurrent.FutureTask.get(FutureTask.java:206) ~[?:1.8.0_141] at org.apache.syncope.core.provisioning.java.ConnectorFacadeProxy.getObject(ConnectorFacadeProxy.java:417) ~[syncope-core-provisioning-java-2.0.10.jar:?] at org.apache.syncope.core.provisioning.java.propagation.AbstractPropagationTaskExecutor.getRemoteObject(AbstractPropagationTaskExecutor.java:641) ~[syncope-core-provisioning-java-2.0.10.jar:2.0.10] at org.apache.syncope.core.provisioning.java.propagation.AbstractPropagationTaskExecutor.execute(AbstractPropagationTaskExecutor.java:421) ~[syncope-core-provisioning-java-2.0.10.jar:2.0.10] at org.apache.syncope.core.provisioning.java.propagation.DefaultPropagationTaskCallable.call(DefaultPropagationTaskCallable.java:89) ~[syncope-core-provisioning-java-2.0.10.jar:2.0.10] at org.apache.syncope.core.provisioning.java.propagation.DefaultPropagationTaskCallable.call(DefaultPropagationTaskCallable.java:38) ~[syncope-core-provisioning-java-2.0.10.jar:2.0.10] at sun.reflect.GeneratedMethodAccessor888.invoke(Unknown Source) ~[?:?] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_141] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_141] at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) ~[spring-aop-4.3.18.RELEASE.jar:4.3.18.RELEASE] at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) ~[spring-aop-4.3.18.RELEASE.jar:4.3.18.RELEASE] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.3.18.RELEASE.jar:4.3.18.RELEASE] at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99) ~[spring-tx-4.3.18.RELEASE.jar:4.3.18.RELEASE] at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:282) ~[spring-tx-4.3.18.RELEASE.jar:4.3.18.RELEASE] at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96) ~[spring-tx-4.3.18.RELEASE.jar:4.3.18.RELEASE] at org.apache.syncope.core.persistence.jpa.spring.DomainTransactionInterceptor.invoke(DomainTransactionInterceptor.java:64) ~[syncope-core-persistence-jpa-2.0.10.jar:2.0.10] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.18.RELEASE.jar:4.3.18.RELEASE] at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213) ~[spring-aop-4.3.18.RELEASE.jar:4.3.18.RELEASE] at com.sun.proxy.$Proxy603.call(Unknown Source) ~[?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_141] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_141] at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_141] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_141] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_141] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_141] Caused by: java.lang.ClassCastException: org.apache.syncope.core.provisioning.java.AsyncConnectorFacade$1 cannot be cast to org.identityconnectors.framework.spi.SearchResultsHandler at org.identityconnectors.framework.impl.api.StreamHandlerUtil$ObjectStreamHandlerAdapter.handle(StreamHandlerUtil.java:103) ~[connector-framework-internal-1.4.4.0.jar:?] at org.identityconnectors.framework.impl.api.BufferedResultsProxy.invoke(BufferedResultsProxy.java:262) ~[connector-framework-internal-1.4.4.0.jar:?] at org.identityconnectors.framework.impl.api.DelegatingTimeoutProxy.invoke(DelegatingTimeoutProxy.java:94) ~[connector-framewor
[jira] [Created] (SYNCOPE-1382) Failure specifying push task filters including db column mapped as integer
fabio martelli created SYNCOPE-1382:
---
Summary: Failure specifying push task filters including db column
mapped as integer
Key: SYNCOPE-1382
URL: https://issues.apache.org/jira/browse/SYNCOPE-1382
Project: Syncope
Issue Type: Improvement
Components: console
Affects Versions: 2.1.1, 2.0.10
Reporter: fabio martelli
Assignee: fabio martelli
Fix For: 2.0.11, 2.1.2, 3.0.0
It seems that case insensitive approach is used for boolean fields mapped on
integer columns.
Failures are experienced with boolean on postgresql. See exception below.
Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: ERROR: function
lower(integer) does not exist
Hint: No function matches the given name and argument types. You might need
to add explicit type casts.
Position: 132 \{prepstmnt 2084826893 SELECT COUNT(any_id) FROM (SELECT
u.any_id FROM (SELECT DISTINCT any_id FROM anyObject_search_attr WHERE
((schema_id='enabled' AND LOWER (booleanvalue)=LOWER(?) AND any_id IN ( SELECT
DISTINCT any_id FROM anyObject_search_attr WHERE schema_id='enabled' AND LOWER
(booleanvalue)=LOWER(?))) AND any_id IN ( SELECT DISTINCT any_id FROM
anyObject_search WHERE type_id=?))) u WHERE u.any_id IN (SELECT any_id FROM
anyObject_search WHERE realm_id IN (SELECT id AS realm_id FROM Realm WHERE id=?
OR id=?))) count_any_id} [code=0, state=42883]
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:218)
~[openjpa-lib-2.4.3.jar:2.4.3]
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:202)
~[openjpa-lib-2.4.3.jar:2.4.3]
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:58)
~[openjpa-lib-2.4.3.jar:2.4.3]
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeQuery(LoggingConnectionDecorator.java:1117)
~[openjpa-lib-2.4.3.jar:2.4.3]
at
org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:268)
~[openjpa-lib-2.4.3.jar:2.4.3]
at
org.apache.openjpa.jdbc.sql.PostgresDictionary$PostgresPreparedStatement.executeQuery(PostgresDictionary.java:1011)
~[openjpa-jdbc-2.4.3.jar:2.4.3]
at
org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:268)
~[openjpa-lib-2.4.3.jar:2.4.3]
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeQuery(JDBCStoreManager.java:1800)
~[openjpa-jdbc-2.4.3.jar:2.4.3]
at
org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:258)
~[openjpa-lib-2.4.3.jar:2.4.3]
at
org.apache.openjpa.jdbc.kernel.SQLStoreQuery$SQLExecutor.executeQuery(SQLStoreQuery.java:317)
~[openjpa-jdbc-2.4.3.jar:2.4.3]
at
org.apache.openjpa.jdbc.kernel.SQLStoreQuery$SQLExecutor.executeQuery(SQLStoreQuery.java:220)
~[openjpa-jdbc-2.4.3.jar:2.4.3]
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:1011)
~[openjpa-kernel-2.4.3.jar:2.4.3]
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:869)
~[openjpa-kernel-2.4.3.jar:2.4.3]
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:800)
~[openjpa-kernel-2.4.3.jar:2.4.3]
at
org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:541)
~[openjpa-kernel-2.4.3.jar:2.4.3]
at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:274)
~[openjpa-persistence-2.4.3.jar:2.4.3]
at
org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:290)
~[openjpa-persistence-2.4.3.jar:2.4.3]
at
org.apache.openjpa.persistence.QueryImpl.getSingleResult(QueryImpl.java:318)
~[openjpa-persistence-2.4.3.jar:2.4.3]
at
org.apache.syncope.core.persistence.jpa.dao.JPAAnySearchDAO.doCount(JPAAnySearchDAO.java:143)
~[syncope-core-persistence-jpa-2.0.10.jar:2.0.10]
at
org.apache.syncope.core.persistence.jpa.dao.AbstractAnySearchDAO.count(AbstractAnySearchDAO.java:129)
~[syncope-core-persistence-jpa-2.0.10.jar:2.0.10]
at
org.apache.syncope.core.provisioning.java.pushpull.PushJobDelegate.doExecuteProvisioning(PushJobDelegate.java:229)
~[syncope-core-provisioning-java-2.0.10.jar:?]
at
org.apache.syncope.core.provisioning.java.pushpull.PushJobDelegate.doExecuteProvisioning(PushJobDelegate.java:57)
~[syncope-core-provisioning-java-2.0.10.jar:?]
at
org.apache.syncope.core.provisioning.java.pushpull.AbstractProvisioningJobDelegate.doExecute(AbstractProvisioningJobDelegate.java:560)
~[syncope-core-provisioning-java-2.0.10.jar:?]
at
org.apache.syncope.core.provisioning.java.job.AbstractSchedTaskJobDelegate.execute(AbstractSchedTaskJobDelegate.java:120)
~[syncope-core-provisioning-java-2.0.10.jar:2.0.10
[jira] [Resolved] (SYNCOPE-1379) Make configurable resource check timeout
[ https://issues.apache.org/jira/browse/SYNCOPE-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1379. - Resolution: Fixed > Make configurable resource check timeout > > > Key: SYNCOPE-1379 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1379 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.0.10, 2.1.1 > Reporter: fabio martelli > Assignee: fabio martelli >Priority: Major > Fix For: 2.0.11, 2.1.2, 3.0.0 > > > Waiting for long timeouts during resource check can negatively affect the > functionality of the console. Give the possibility to disable or configure > check timeouts, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1379) Make configurable resource check timeout
fabio martelli created SYNCOPE-1379: --- Summary: Make configurable resource check timeout Key: SYNCOPE-1379 URL: https://issues.apache.org/jira/browse/SYNCOPE-1379 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 2.1.1, 2.0.10 Reporter: fabio martelli Assignee: fabio martelli Fix For: 2.0.11, 2.1.2, 3.0.0 Waiting for long timeouts during resource check can negatively affect the functionality of the console. Give the possibility to disable or configure check timeouts, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1375) The existence of a membership attribute mapping implies membership creation during pull
[ https://issues.apache.org/jira/browse/SYNCOPE-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1375. - Resolution: Fixed > The existence of a membership attribute mapping implies membership creation > during pull > --- > > Key: SYNCOPE-1375 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1375 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.10, 2.1.1 > Reporter: fabio martelli >Assignee: fabio martelli >Priority: Major > Fix For: 2.0.11, 2.1.2, 3.0.0 > > > Just the fact that a mapping for a membership attribute exists will imply the > creation of the relative membership during pull. This behavior occurs also in > case no membership rules or membership attribute values are retrieved from > external resource. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1375) The existence of a membership attribute mapping implies membership creation during pull
fabio martelli created SYNCOPE-1375: --- Summary: The existence of a membership attribute mapping implies membership creation during pull Key: SYNCOPE-1375 URL: https://issues.apache.org/jira/browse/SYNCOPE-1375 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.1.1, 2.0.10 Reporter: fabio martelli Assignee: fabio martelli Fix For: 2.0.11, 2.1.2, 3.0.0 Just the fact that a mapping for a membership attribute exists will imply the creation of the relative membership during pull. This behavior occurs also in case no membership rules or membership attribute values are retrieved from external resource. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1361) Custom audit appender does not work after a restart
[ https://issues.apache.org/jira/browse/SYNCOPE-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1361. - Resolution: Fixed > Custom audit appender does not work after a restart > --- > > Key: SYNCOPE-1361 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1361 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.10, 2.1.1 > Reporter: fabio martelli > Assignee: fabio martelli >Priority: Major > Fix For: 2.0.11, 2.1.2, 3.0.0 > > > When Syncope restarts defined custom appenders stop working. > In order to have them working again tick/untick in configuration audit > section is required. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1361) Custom audit appender does not work after a restart
[ https://issues.apache.org/jira/browse/SYNCOPE-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli reassigned SYNCOPE-1361: --- Assignee: fabio martelli > Custom audit appender does not work after a restart > --- > > Key: SYNCOPE-1361 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1361 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.10, 2.1.1 > Reporter: fabio martelli > Assignee: fabio martelli >Priority: Major > Fix For: 2.0.11, 2.1.2, 3.0.0 > > > When Syncope restarts defined custom appenders stop working. > In order to have them working again tick/untick in configuration audit > section is required. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SYNCOPE-1361) Custom audit appender does not work after a restart
[ https://issues.apache.org/jira/browse/SYNCOPE-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli updated SYNCOPE-1361: Fix Version/s: 3.0.0 > Custom audit appender does not work after a restart > --- > > Key: SYNCOPE-1361 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1361 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.10, 2.1.1 > Reporter: fabio martelli >Priority: Major > Fix For: 2.0.11, 2.1.2, 3.0.0 > > > When Syncope restarts defined custom appenders stop working. > In order to have them working again tick/untick in configuration audit > section is required. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1361) Custom audit appender does not work after a restart
fabio martelli created SYNCOPE-1361: --- Summary: Custom audit appender does not work after a restart Key: SYNCOPE-1361 URL: https://issues.apache.org/jira/browse/SYNCOPE-1361 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.1.1, 2.0.10 Reporter: fabio martelli Fix For: 2.0.11, 2.1.2 When Syncope restarts defined custom appenders stop working. In order to have them working again tick/untick in configuration audit section is required. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [VOTE] Apache Syncope 2.1.1
Il 17/08/2018 11:15, Francesco Chicchiriccò ha scritto: I've created a 2.1.1 release, with the following artifacts up for a vote: GIT source tag (a9022c6c2cb8ccba306e0aa4a65f7f60c40ed5d9): https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=a9022c6c2cb8ccba306e0aa4a65f7f60c40ed5d9 List of changes: https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=80c7c2180ca84f0e7aa04b4cae4c69c3711aace4;hb=a9022c6c2cb8ccba306e0aa4a65f7f60c40ed5d9 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.1/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1052/ Staging site: http://syncope.apache.org/2.1.1/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. +1 Regards -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
Re: [VOTE] Apache Syncope 2.0.10
Il 17/08/2018 11:15, Francesco Chicchiriccò ha scritto: I've created a 2.0.10 release, with the following artifacts up for a vote: GIT source tag (7081e00f2501c3fed3f124d5ccd601e494e94557): https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=7081e00f2501c3fed3f124d5ccd601e494e94557 List of changes: https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=70fa4ae05bbef053f83d4d1132153f3bc77e0edf;hb=7081e00f2501c3fed3f124d5ccd601e494e94557 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.0.10/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1053/ Staging site (yes, same as for 2.1.1, not a typo): http://syncope.apache.org/2.1.1/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. +1 Regards -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
[jira] [Resolved] (SYNCOPE-1340) Cannot update membership attribute
[ https://issues.apache.org/jira/browse/SYNCOPE-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1340. - Resolution: Fixed > Cannot update membership attribute > -- > > Key: SYNCOPE-1340 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1340 > Project: Syncope > Issue Type: Bug > Components: common >Affects Versions: 2.0.9, 2.1.0 > Reporter: fabio martelli > Assignee: fabio martelli >Priority: Major > Fix For: 2.0.10, 2.1.1, 3.0.0 > > > It seems that there is a failure evaluating the diff of entities involving > membership attributes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1340) Cannot update membership attribute
fabio martelli created SYNCOPE-1340: --- Summary: Cannot update membership attribute Key: SYNCOPE-1340 URL: https://issues.apache.org/jira/browse/SYNCOPE-1340 Project: Syncope Issue Type: Bug Components: common Affects Versions: 2.1.0, 2.0.9 Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.0.10, 2.1.1, 3.0.0 It seems that there is a failure evaluating the diff of entities involving membership attributes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1333) Missing virtual attribute value in case of type extension
[ https://issues.apache.org/jira/browse/SYNCOPE-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1333. - Resolution: Fixed > Missing virtual attribute value in case of type extension > - > > Key: SYNCOPE-1333 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1333 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.9, 2.1.0 > Reporter: fabio martelli > Assignee: fabio martelli >Priority: Major > Fix For: 2.0.10, 2.1.1 > > > In case of virtual attribute assigned to an class used as group type > extension the value is not shown into the administration console, among > membership virtual attributes. > Steps: > * define a virtual attribute > * assign it to an object class to be used as type extension of a group > * create or update a user and assign the group above > * edit again the user and check for the value into the wizard step about the > virtual attributes, among membership attributes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SYNCOPE-1333) Missing virtual attribute value in case of type extension
[ https://issues.apache.org/jira/browse/SYNCOPE-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli updated SYNCOPE-1333: Description: In case of virtual attribute assigned to an class used as group type extension the value is not shown into the administration console, among membership virtual attributes. Steps: * define a virtual attribute * assign it to an object class to be used as type extension of a group * create or update a user and assign the group above * edit again the user and check for the value into the wizard step about the virtual attributes, among membership attributes was: In case of virtual attribute assigned to an class used as group type extension the value is not shown into the administration console, among membership virtual attributes. Steps: * define a virtual attribute * assign it to an object class to be used as type extension of a group * create or update a user and assign the group above * edit again the user and check for the value into the wizard step about the virtual attributes, among membership attributes Actually I'm not sure the problem is limited to the console only > Missing virtual attribute value in case of type extension > - > > Key: SYNCOPE-1333 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1333 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.9, 2.1.0 > Reporter: fabio martelli > Assignee: fabio martelli >Priority: Major > Fix For: 2.0.10, 2.1.1 > > > In case of virtual attribute assigned to an class used as group type > extension the value is not shown into the administration console, among > membership virtual attributes. > Steps: > * define a virtual attribute > * assign it to an object class to be used as type extension of a group > * create or update a user and assign the group above > * edit again the user and check for the value into the wizard step about the > virtual attributes, among membership attributes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SYNCOPE-1333) Missing virtual attribute value in case of type extension
[ https://issues.apache.org/jira/browse/SYNCOPE-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli updated SYNCOPE-1333: Description: In case of virtual attribute assigned to an class used as group type extension the value is not shown into the administration console, among membership virtual attributes. Steps: * define a virtual attribute * assign it to an object class to be used as type extension of a group * create or update a user and assign the group above * edit again the user and check for the value into the wizard step about the virtual attributes, among membership attributes Actually I'm not sure the problem is limited to the console only was: In case of virtual attribute assigned to an class used as group auxiliary class the value is not shown into the administration console, among membership virtual attributes. Steps: * define a virtual attribute * assign it to an object class to be used as auxiliary class of a group * create or update a user and assign the group above * edit again the user and check for the value into the wizard step about the virtual attributes, among membership attributes Actually I'm not sure the problem is limited to the console only Summary: Missing virtual attribute value in case of type extension (was: Missing virtual attribute value in case of auxiliary class) > Missing virtual attribute value in case of type extension > - > > Key: SYNCOPE-1333 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1333 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.9, 2.1.0 > Reporter: fabio martelli > Assignee: fabio martelli >Priority: Major > Fix For: 2.0.10, 2.1.1 > > > In case of virtual attribute assigned to an class used as group type > extension the value is not shown into the administration console, among > membership virtual attributes. > Steps: > * define a virtual attribute > * assign it to an object class to be used as type extension of a group > * create or update a user and assign the group above > * edit again the user and check for the value into the wizard step about the > virtual attributes, among membership attributes > Actually I'm not sure the problem is limited to the console only -- This message was sent by Atlassian JIRA (v7.6.3#76005)
