[jira] [Updated] (SYNCOPE-1829) Pull by subscription
[
https://issues.apache.org/jira/browse/SYNCOPE-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-1829:
Description:
There have been a few use cases where Syncope was requested to "import" users
by subscribing to some sort of queue, like as Apache Kafka / ActiveMQ, Google
PubSub, etc.
A more general mechanism can be implemented, to generate pull events (e.g.
ConnId's {{SyncDelta}} objects) from messages received via queue subscription.
Then we could provide one or more implementations, one for each queue
technology - the ones mentioned above, but even more if needed.
Also, there should be a flexible, extensible way to transform the message
payload into a {{SyncDelta}} instance.
was:
There have been a few use cases where Syncope was requested to "import" users
by subscribing to some sort of queue, like as Apache Kafka / ActiveMQ, Google
PubSub, etc.
A more general mechanism can be implemented, to generate pull events (e.g.
ConnId's {{SyncDelta}} objects) from messages received via queue subscription.
Then we could provide one or more implementation for each queue technology -
the ones mentioned above, but even more if needed.
> Pull by subscription
>
>
> Key: SYNCOPE-1829
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1829
> Project: Syncope
> Issue Type: New Feature
>Reporter: Francesco Chicchiriccò
>Priority: Major
> Fix For: 4.0.0
>
>
> There have been a few use cases where Syncope was requested to "import" users
> by subscribing to some sort of queue, like as Apache Kafka / ActiveMQ, Google
> PubSub, etc.
> A more general mechanism can be implemented, to generate pull events (e.g.
> ConnId's {{SyncDelta}} objects) from messages received via queue subscription.
> Then we could provide one or more implementations, one for each queue
> technology - the ones mentioned above, but even more if needed.
> Also, there should be a flexible, extensible way to transform the message
> payload into a {{SyncDelta}} instance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1829) Pull by subscription
[
https://issues.apache.org/jira/browse/SYNCOPE-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-1829:
Description:
There have been a few use cases where Syncope was requested to "import" users
by subscribing to some sort of queue, like as Apache Kafka / ActiveMQ, Google
PubSub, etc.
A more general mechanism can be implemented, to generate pull events (e.g.
ConnId's {{SyncDelta}} objects) from messages received via queue subscription.
Then we could provide one or more implementation for each queue technology -
the ones mentioned above, but even more if needed.
was:
There have been a few use cases where Syncope was requested to "import" users
by subscribing to some sort of queue, like as Apache Kafka / ActiveMQ, Google
PubSub, etc.
A more general mechanism can be implemented, to generate pull events (e.g.
ConnId's {{SyncDelta}} objects) from messages received via queue subscription.
Then we could provide one or more implementation specific to the queue
technologies - the ones mentioned above, but even more if needed.
> Pull by subscription
>
>
> Key: SYNCOPE-1829
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1829
> Project: Syncope
> Issue Type: New Feature
>Reporter: Francesco Chicchiriccò
>Priority: Major
> Fix For: 4.0.0
>
>
> There have been a few use cases where Syncope was requested to "import" users
> by subscribing to some sort of queue, like as Apache Kafka / ActiveMQ, Google
> PubSub, etc.
> A more general mechanism can be implemented, to generate pull events (e.g.
> ConnId's {{SyncDelta}} objects) from messages received via queue subscription.
> Then we could provide one or more implementation for each queue technology -
> the ones mentioned above, but even more if needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SYNCOPE-1829) Pull by subscription
Francesco Chicchiriccò created SYNCOPE-1829:
---
Summary: Pull by subscription
Key: SYNCOPE-1829
URL: https://issues.apache.org/jira/browse/SYNCOPE-1829
Project: Syncope
Issue Type: New Feature
Reporter: Francesco Chicchiriccò
Fix For: 4.0.0
There have been a few use cases where Syncope was requested to "import" users
by subscribing to some sort of queue, like as Apache Kafka / ActiveMQ, Google
PubSub, etc.
A more general mechanism can be implemented, to generate pull events (e.g.
ConnId's {{SyncDelta}} objects) from messages received via queue subscription.
Then we coul provide one or more implementation specific to the queue
technologies - the ones mentioned above, but even more if needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1829) Pull by subscription
[
https://issues.apache.org/jira/browse/SYNCOPE-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-1829:
Description:
There have been a few use cases where Syncope was requested to "import" users
by subscribing to some sort of queue, like as Apache Kafka / ActiveMQ, Google
PubSub, etc.
A more general mechanism can be implemented, to generate pull events (e.g.
ConnId's {{SyncDelta}} objects) from messages received via queue subscription.
Then we could provide one or more implementation specific to the queue
technologies - the ones mentioned above, but even more if needed.
was:
There have been a few use cases where Syncope was requested to "import" users
by subscribing to some sort of queue, like as Apache Kafka / ActiveMQ, Google
PubSub, etc.
A more general mechanism can be implemented, to generate pull events (e.g.
ConnId's {{SyncDelta}} objects) from messages received via queue subscription.
Then we coul provide one or more implementation specific to the queue
technologies - the ones mentioned above, but even more if needed.
> Pull by subscription
>
>
> Key: SYNCOPE-1829
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1829
> Project: Syncope
> Issue Type: New Feature
>Reporter: Francesco Chicchiriccò
>Priority: Major
> Fix For: 4.0.0
>
>
> There have been a few use cases where Syncope was requested to "import" users
> by subscribing to some sort of queue, like as Apache Kafka / ActiveMQ, Google
> PubSub, etc.
> A more general mechanism can be implemented, to generate pull events (e.g.
> ConnId's {{SyncDelta}} objects) from messages received via queue subscription.
> Then we could provide one or more implementation specific to the queue
> technologies - the ones mentioned above, but even more if needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1828) Can't open the profiles tab in WA page if one of the fields is null
[ https://issues.apache.org/jira/browse/SYNCOPE-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1828. - Resolution: Fixed > Can't open the profiles tab in WA page if one of the fields is null > --- > > Key: SYNCOPE-1828 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1828 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 3.0.8 >Reporter: Samuel Garofalo >Assignee: Samuel Garofalo >Priority: Major > Fix For: 3.0.9, 4.0.0 > > > Create an auth profile entry with _u2fRegisteredDevices_ or > _impersonationAccounts_ to null and go to profiles tab in WA page, the tab > will not open. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1828) Can't open the profiles tab in WA page if one of the fields is null
[ https://issues.apache.org/jira/browse/SYNCOPE-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886876#comment-17886876 ] ASF subversion and git services commented on SYNCOPE-1828: -- Commit 5d1f4cf9f780a57a368288ef7026979a3430f604 in syncope's branch refs/heads/master from Samuel Garofalo [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=5d1f4cf9f7 ] [SYNCOPE-1828] check on null value (#857) > Can't open the profiles tab in WA page if one of the fields is null > --- > > Key: SYNCOPE-1828 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1828 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 3.0.8 >Reporter: Samuel Garofalo >Assignee: Samuel Garofalo >Priority: Major > Fix For: 3.0.9, 4.0.0 > > > Create an auth profile entry with _u2fRegisteredDevices_ or > _impersonationAccounts_ to null and go to profiles tab in WA page, the tab > will not open. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1828) Can't open the profiles tab in WA page if one of the fields is null
[ https://issues.apache.org/jira/browse/SYNCOPE-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886875#comment-17886875 ] ASF subversion and git services commented on SYNCOPE-1828: -- Commit f0b1bebf90bc96578fb0fa97e53b9558075bdf3f in syncope's branch refs/heads/3_0_X from Samuel Garofalo [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=f0b1bebf90 ] [SYNCOPE-1828] check on null value (#857) > Can't open the profiles tab in WA page if one of the fields is null > --- > > Key: SYNCOPE-1828 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1828 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 3.0.8 >Reporter: Samuel Garofalo >Assignee: Samuel Garofalo >Priority: Major > Fix For: 3.0.9, 4.0.0 > > > Create an auth profile entry with _u2fRegisteredDevices_ or > _impersonationAccounts_ to null and go to profiles tab in WA page, the tab > will not open. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SYNCOPE-1828) Can't open the profiles tab in WA page if one of the fields is null
[ https://issues.apache.org/jira/browse/SYNCOPE-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Garofalo reassigned SYNCOPE-1828: Assignee: Samuel Garofalo > Can't open the profiles tab in WA page if one of the fields is null > --- > > Key: SYNCOPE-1828 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1828 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 3.0.8 >Reporter: Samuel Garofalo >Assignee: Samuel Garofalo >Priority: Major > Fix For: 3.0.9, 4.0.0 > > > Create an auth profile entry with _u2fRegisteredDevices_ or > _impersonationAccounts_ to null and go to profiles tab in WA page, the tab > will not open. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1828) Can't open the profiles tab in WA page if one of the fields is null
Samuel Garofalo created SYNCOPE-1828: Summary: Can't open the profiles tab in WA page if one of the fields is null Key: SYNCOPE-1828 URL: https://issues.apache.org/jira/browse/SYNCOPE-1828 Project: Syncope Issue Type: Bug Components: console Affects Versions: 3.0.8 Reporter: Samuel Garofalo Fix For: 3.0.9, 4.0.0 Create an auth profile entry with _u2fRegisteredDevices_ or _impersonationAccounts_ to null and go to profiles tab in WA page, the tab will not open. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1827) Remove non-JSON JPA support
[
https://issues.apache.org/jira/browse/SYNCOPE-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-1827.
-
Resolution: Fixed
> Remove non-JSON JPA support
> ---
>
> Key: SYNCOPE-1827
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1827
> Project: Syncope
> Issue Type: Task
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 4.0.0
>
>
> Historically, JPA support was provided since the beginning under
> {{core/persistence-jpa}}.
> At a certain point, some way to leverage the possibility to manipulate JSON
> strings for user, group and any object attributes was introduced for
> PostgreSQL first, then MySQL, Oracle and finally MariaDB. The purpose: higher
> throughput and lower search operation roundups.
> Such "flavors" were implemented under {{core/persistence-jpa-json}}.
> It's been quite some time, however, that all new deployments have been
> starting directly with one of JSON flavors rather than with their non-JSON,
> original, counterparts.
> The
> [proposal|https://lists.apache.org/thread/xkh85f8hv83lz3cmlfxkhj45bmt9hz6c]
> to keep, for 4.0 onwards, only such JSON flavors was discussed and found no
> arguments against.
> Removing the non-JSON flavors will result in simplified code, easier to
> maintain.
> One side issue of such a proposal is that Syncope 4.0 will not be able to run
> on H2 any more. H2 is currently used for several unit tests, integration test
> profiles, standalone and even in the embedded profile for archetype.
> To solve this, we will be leveraging [embedded
> PostgreSQL|https://github.com/zonkyio/embedded-postgres], a nice AL-2.0
> project which provides support to run a PostgreSQL instance, without Docker,
> on all major platforms including GNU / Linux, Mac OS and Windows.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1827) Remove non-JSON JPA support
[
https://issues.apache.org/jira/browse/SYNCOPE-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881629#comment-17881629
]
ASF subversion and git services commented on SYNCOPE-1827:
--
Commit c4f2a8b0f359a1cdc354cb06f2dfa92509245fee in syncope's branch
refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=c4f2a8b0f3 ]
[SYNCOPE-1827] Only JPA with JSON support available, PostgreSQL the default
option (#820)
> Remove non-JSON JPA support
> ---
>
> Key: SYNCOPE-1827
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1827
> Project: Syncope
> Issue Type: Task
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 4.0.0
>
>
> Historically, JPA support was provided since the beginning under
> {{core/persistence-jpa}}.
> At a certain point, some way to leverage the possibility to manipulate JSON
> strings for user, group and any object attributes was introduced for
> PostgreSQL first, then MySQL, Oracle and finally MariaDB. The purpose: higher
> throughput and lower search operation roundups.
> Such "flavors" were implemented under {{core/persistence-jpa-json}}.
> It's been quite some time, however, that all new deployments have been
> starting directly with one of JSON flavors rather than with their non-JSON,
> original, counterparts.
> The
> [proposal|https://lists.apache.org/thread/xkh85f8hv83lz3cmlfxkhj45bmt9hz6c]
> to keep, for 4.0 onwards, only such JSON flavors was discussed and found no
> arguments against.
> Removing the non-JSON flavors will result in simplified code, easier to
> maintain.
> One side issue of such a proposal is that Syncope 4.0 will not be able to run
> on H2 any more. H2 is currently used for several unit tests, integration test
> profiles, standalone and even in the embedded profile for archetype.
> To solve this, we will be leveraging [embedded
> PostgreSQL|https://github.com/zonkyio/embedded-postgres], a nice AL-2.0
> project which provides support to run a PostgreSQL instance, without Docker,
> on all major platforms including GNU / Linux, Mac OS and Windows.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SYNCOPE-1827) Remove non-JSON JPA support
Francesco Chicchiriccò created SYNCOPE-1827:
---
Summary: Remove non-JSON JPA support
Key: SYNCOPE-1827
URL: https://issues.apache.org/jira/browse/SYNCOPE-1827
Project: Syncope
Issue Type: Task
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
Fix For: 4.0.0
Historically, JPA support was provided since the beginning under
{{core/persistence-jpa}}.
At a certain point, some way to leverage the possibility to manipulate JSON
strings for user, group and any object attributes was introduced for PostgreSQL
first, then MySQL, Oracle and finally MariaDB. The purpose: higher throughput
and lower search operation roundups.
Such "flavors" were implemented under {{core/persistence-jpa-json}}.
It's been quite some time, however, that all new deployments have been starting
directly with one of JSON flavors rather than with their non-JSON, original,
counterparts.
The [proposal|https://lists.apache.org/thread/xkh85f8hv83lz3cmlfxkhj45bmt9hz6c]
to keep, for 4.0 onwards, only such JSON flavors was discussed and found no
arguments against.
Removing the non-JSON flavors will result in simplified code, easier to
maintain.
One side issue of such a proposal is that Syncope 4.0 will not be able to run
on H2 any more. H2 is currently used for several unit tests, integration test
profiles, standalone and even in the embedded profile for archetype.
To solve this, we will be leveraging [embedded
PostgreSQL|https://github.com/zonkyio/embedded-postgres], a nice AL-2.0 project
which provides support to run a PostgreSQL instance, without Docker, on all
major platforms including GNU / Linux, Mac OS and Windows.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1826) Search fails if search condition contains four digits at the end of the value
[ https://issues.apache.org/jira/browse/SYNCOPE-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-1826. Resolution: Resolved > Search fails if search condition contains four digits at the end of the value > - > > Key: SYNCOPE-1826 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1826 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.8 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Major > Fix For: 3.0.9, 4.0.0 > > > Suppose to create a user, group or any object with username/name or any other > attribute with value like "sh test app 0722" (ending with four digits). Then > search for that user with the specific search condition: search is not going > to return any result. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1826) Search fails if search condition contains four digits at the end of the value
[ https://issues.apache.org/jira/browse/SYNCOPE-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871320#comment-17871320 ] ASF subversion and git services commented on SYNCOPE-1826: -- Commit 318db330a7b5bd1359bfcba9280549d84684087f in syncope's branch refs/heads/master from Andrea Patricelli [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=318db330a7 ] [SYNCOPE-1826] ensuring to correctly handle plus in fiql and make search with four digits work (#804) * [SYNCOPE-1826] ensuring to correctly handle plus in fiql and make search with four digits work > Search fails if search condition contains four digits at the end of the value > - > > Key: SYNCOPE-1826 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1826 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.8 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Major > Fix For: 3.0.9, 4.0.0 > > > Suppose to create a user, group or any object with username/name or any other > attribute with value like "sh test app 0722" (ending with four digits). Then > search for that user with the specific search condition: search is not going > to return any result. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1826) Search fails if search condition contains four digits at the end of the value
[ https://issues.apache.org/jira/browse/SYNCOPE-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871313#comment-17871313 ] ASF subversion and git services commented on SYNCOPE-1826: -- Commit 130b7e019338dc6b8bd4294ebe5eca4be5fcce25 in syncope's branch refs/heads/3_0_X from Andrea Patricelli [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=130b7e0193 ] [SYNCOPE-1826] ensuring to correctly handle plus in fiql and make search with four digits work (#804) * [SYNCOPE-1826] ensuring to correctly handle plus in fiql and make search with four digits work > Search fails if search condition contains four digits at the end of the value > - > > Key: SYNCOPE-1826 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1826 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.8 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Major > Fix For: 3.0.9, 4.0.0 > > > Suppose to create a user, group or any object with username/name or any other > attribute with value like "sh test app 0722" (ending with four digits). Then > search for that user with the specific search condition: search is not going > to return any result. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1826) Search fails if search condition contains four digits at the end of the value
[ https://issues.apache.org/jira/browse/SYNCOPE-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-1826: --- Description: Suppose to create a user, group or any object with username/name or any other attribute with value like "sh test app 0722" (ending with four digits). Then search for that user with the specific search condition: search is not going to return any result. was: Suppose to create a user, group or any object with username/name or any other attribute with value like "sh test app 0722" (ending with four digits). Then search for that user with the specific search condition. Search is not going to return any result. > Search fails if search condition contains four digits at the end of the value > - > > Key: SYNCOPE-1826 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1826 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.8 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Major > Fix For: 3.0.9, 4.0.0 > > > Suppose to create a user, group or any object with username/name or any other > attribute with value like "sh test app 0722" (ending with four digits). Then > search for that user with the specific search condition: search is not going > to return any result. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1826) Search fails if search condition contains four digits at the end of the value
Andrea Patricelli created SYNCOPE-1826: -- Summary: Search fails if search condition contains four digits at the end of the value Key: SYNCOPE-1826 URL: https://issues.apache.org/jira/browse/SYNCOPE-1826 Project: Syncope Issue Type: Bug Components: core Affects Versions: 3.0.8 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 3.0.9, 4.0.0 Suppose to create a user, group or any object with username/name or any other attribute with value like "sh test app 0722" (ending with four digits). Then search for that user with the specific search condition. Search is not going to return any result. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1825) Database schema not set on OpenJPA even if configured by properties
[
https://issues.apache.org/jira/browse/SYNCOPE-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-1825.
-
Resolution: Fixed
> Database schema not set on OpenJPA even if configured by properties
> ---
>
> Key: SYNCOPE-1825
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1825
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 3.0.8
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Labels: jpa, oracle
> Fix For: 3.0.9
>
>
> When running Syncope Core on Oracle database persistence with multi-tenant
> setup, it was noticed that further Domains besides {{Master}} were unable to
> create the expected tables and constraints.
> This situation was reported only when configuring multiple database schema in
> the same Oracle database deployment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1825) Database schema not set on OpenJPA even if configured by properties
[
https://issues.apache.org/jira/browse/SYNCOPE-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870459#comment-17870459
]
ASF subversion and git services commented on SYNCOPE-1825:
--
Commit 089fe5adbb73647167978bd2afadb1c0a1395a7a in syncope's branch
refs/heads/3_0_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=089fe5adbb ]
[SYNCOPE-1825] Ensuring to pass dbSchema, if available, as openjpa.jdbc.Schema
(#802)
> Database schema not set on OpenJPA even if configured by properties
> ---
>
> Key: SYNCOPE-1825
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1825
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 3.0.8
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Labels: jpa, oracle
> Fix For: 3.0.9
>
>
> When running Syncope Core on Oracle database persistence with multi-tenant
> setup, it was noticed that further Domains besides {{Master}} were unable to
> create the expected tables and constraints.
> This situation was reported only when configuring multiple database schema in
> the same Oracle database deployment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1825) Database schema not set on OpenJPA even if configured by properties
[
https://issues.apache.org/jira/browse/SYNCOPE-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-1825:
Fix Version/s: (was: 4.0.0)
> Database schema not set on OpenJPA even if configured by properties
> ---
>
> Key: SYNCOPE-1825
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1825
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 3.0.8
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Labels: jpa, oracle
> Fix For: 3.0.9
>
>
> When running Syncope Core on Oracle database persistence with multi-tenant
> setup, it was noticed that further Domains besides {{Master}} were unable to
> create the expected tables and constraints.
> This situation was reported only when configuring multiple database schema in
> the same Oracle database deployment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SYNCOPE-1825) Database schema not set on OpenJPA even if configured by properties
Francesco Chicchiriccò created SYNCOPE-1825:
---
Summary: Database schema not set on OpenJPA even if configured by
properties
Key: SYNCOPE-1825
URL: https://issues.apache.org/jira/browse/SYNCOPE-1825
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 3.0.8
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
Fix For: 3.0.9, 4.0.0
When running Syncope Core on Oracle database persistence with multi-tenant
setup, it was noticed that further Domains besides {{Master}} were unable to
create the expected tables and constraints.
This situation was reported only when configuring multiple database schema in
the same Oracle database deployment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1824) Password policies are not always enforced on linked account password while updating account
[ https://issues.apache.org/jira/browse/SYNCOPE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-1824. Resolution: Resolved > Password policies are not always enforced on linked account password while > updating account > --- > > Key: SYNCOPE-1824 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1824 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.8 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Major > Fix For: 3.0.9, 4.0.0 > > > Given a user with one or more linked accounts associated, update one or more > linked account passwords only, without changing the user password. > Password policies are not enforced and even not compliant password are going > to be accepted, resulting in further errors while updating the user password. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SYNCOPE-1824) Password policies are not always enforced on linked account password while updating account
[ https://issues.apache.org/jira/browse/SYNCOPE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli reassigned SYNCOPE-1824: -- Assignee: Andrea Patricelli > Password policies are not always enforced on linked account password while > updating account > --- > > Key: SYNCOPE-1824 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1824 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.8 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Major > Fix For: 3.0.9, 4.0.0 > > > Given a user with one or more linked accounts associated, update one or more > linked account passwords only, without changing the user password. > Password policies are not enforced and even not compliant password are going > to be accepted, resulting in further errors while updating the user password. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1824) Password policies are not always enforced on linked account password while updating account
[ https://issues.apache.org/jira/browse/SYNCOPE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869884#comment-17869884 ] ASF subversion and git services commented on SYNCOPE-1824: -- Commit 3267a1b36e7ac6f1b592c771db3e881cb0c2c01c in syncope's branch refs/heads/master from Andrea Patricelli [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=3267a1b36e ] [SYNCOPE-1824] ensuring linked account password validation on linked account (only) update (#799) > Password policies are not always enforced on linked account password while > updating account > --- > > Key: SYNCOPE-1824 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1824 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.8 >Reporter: Andrea Patricelli >Priority: Major > Fix For: 3.0.9, 4.0.0 > > > Given a user with one or more linked accounts associated, update one or more > linked account passwords only, without changing the user password. > Password policies are not enforced and even not compliant password are going > to be accepted, resulting in further errors while updating the user password. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1824) Password policies are not always enforced on linked account password while updating account
[ https://issues.apache.org/jira/browse/SYNCOPE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869882#comment-17869882 ] ASF subversion and git services commented on SYNCOPE-1824: -- Commit be12989c30f1f8cf8c99a68c87aad8f19d60a657 in syncope's branch refs/heads/3_0_X from Andrea Patricelli [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=be12989c30 ] [SYNCOPE-1824] ensuring linked account password validation on linked account (only) update (#799) > Password policies are not always enforced on linked account password while > updating account > --- > > Key: SYNCOPE-1824 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1824 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.8 >Reporter: Andrea Patricelli >Priority: Major > Fix For: 3.0.9, 4.0.0 > > > Given a user with one or more linked accounts associated, update one or more > linked account passwords only, without changing the user password. > Password policies are not enforced and even not compliant password are going > to be accepted, resulting in further errors while updating the user password. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1824) Password policies are not always enforced on linked account password while updating account
Andrea Patricelli created SYNCOPE-1824: -- Summary: Password policies are not always enforced on linked account password while updating account Key: SYNCOPE-1824 URL: https://issues.apache.org/jira/browse/SYNCOPE-1824 Project: Syncope Issue Type: Bug Components: core Affects Versions: 3.0.8 Reporter: Andrea Patricelli Fix For: 3.0.9, 4.0.0 Given a user with one or more linked accounts associated, update one or more linked account passwords only, without changing the user password. Password policies are not enforced and even not compliant password are going to be accepted, resulting in further errors while updating the user password. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1662) Leverage MariaDB JSON type
[ https://issues.apache.org/jira/browse/SYNCOPE-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1662. - Resolution: Fixed > Leverage MariaDB JSON type > -- > > Key: SYNCOPE-1662 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1662 > Project: Syncope > Issue Type: New Feature > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Labels: jpa, mariadb, persistence > Fix For: 3.0.9, 4.0.0 > > > Similar to SYNCOPE-1395 for PostgreSQL and SYNCOPE-1401 for MySQL, enhance > the JPA layer by empowering [MariaDB JSON > datatype|https://mariadb.com/kb/en/json-data-type/] for user, group and any > object attributes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1662) Leverage MariaDB JSON type
[ https://issues.apache.org/jira/browse/SYNCOPE-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869332#comment-17869332 ] ASF subversion and git services commented on SYNCOPE-1662: -- Commit 3d595b642d82c17ee44de499d73bab0da6a86a1a in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=3d595b642d ] [SYNCOPE-1662] Introducing JSON support for MariaDB (#798) > Leverage MariaDB JSON type > -- > > Key: SYNCOPE-1662 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1662 > Project: Syncope > Issue Type: New Feature > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Labels: jpa, mariadb, persistence > Fix For: 3.0.9, 4.0.0 > > > Similar to SYNCOPE-1395 for PostgreSQL and SYNCOPE-1401 for MySQL, enhance > the JPA layer by empowering [MariaDB JSON > datatype|https://mariadb.com/kb/en/json-data-type/] for user, group and any > object attributes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1662) Leverage MariaDB JSON type
[
https://issues.apache.org/jira/browse/SYNCOPE-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868925#comment-17868925
]
Francesco Chicchiriccò commented on SYNCOPE-1662:
-
The JSON support for MariaDB is introduced with a couple of limitations:
# [MDEV-27898|https://jira.mariadb.org/browse/MDEV-27898]: user {{root}} is
needed
# [MDEV-34644|https://jira.mariadb.org/browse/MDEV-34644]: the search views
cannot be created as done for MySQL, hence search operations are not
implemented by full leveraging JSON features
> Leverage MariaDB JSON type
> --
>
> Key: SYNCOPE-1662
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1662
> Project: Syncope
> Issue Type: New Feature
> Components: core
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Labels: jpa, mariadb, persistence
> Fix For: 3.0.9, 4.0.0
>
>
> Similar to SYNCOPE-1395 for PostgreSQL and SYNCOPE-1401 for MySQL, enhance
> the JPA layer by empowering [MariaDB JSON
> datatype|https://mariadb.com/kb/en/json-data-type/] for user, group and any
> object attributes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1662) Leverage MariaDB JSON type
[ https://issues.apache.org/jira/browse/SYNCOPE-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868924#comment-17868924 ] ASF subversion and git services commented on SYNCOPE-1662: -- Commit 78e28a7ddcc4126352363f2d02a1e39d6d6cabaa in syncope's branch refs/heads/3_0_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=78e28a7ddc ] [SYNCOPE-1662] Introducing JSON support for MariaDB (#797) > Leverage MariaDB JSON type > -- > > Key: SYNCOPE-1662 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1662 > Project: Syncope > Issue Type: New Feature > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Labels: jpa, mariadb, persistence > Fix For: 3.0.9, 4.0.0 > > > Similar to SYNCOPE-1395 for PostgreSQL and SYNCOPE-1401 for MySQL, enhance > the JPA layer by empowering [MariaDB JSON > datatype|https://mariadb.com/kb/en/json-data-type/] for user, group and any > object attributes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SYNCOPE-1662) Leverage MariaDB JSON type
[ https://issues.apache.org/jira/browse/SYNCOPE-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-1662: --- Assignee: Francesco Chicchiriccò > Leverage MariaDB JSON type > -- > > Key: SYNCOPE-1662 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1662 > Project: Syncope > Issue Type: New Feature > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Labels: jpa, mariadb, persistence > Fix For: 3.0.9, 4.0.0 > > > Similar to SYNCOPE-1395 for PostgreSQL and SYNCOPE-1401 for MySQL, enhance > the JPA layer by empowering [MariaDB JSON > datatype|https://mariadb.com/kb/en/json-data-type/] for user, group and any > object attributes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1758) NullPointer exception at WA refresh time during startup
[
https://issues.apache.org/jira/browse/SYNCOPE-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-1758:
Fix Version/s: (was: 4.0.0)
(was: 3.0.8)
> 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
>Priority: Minor
>
> 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.DefaultCasCon
[jira] [Updated] (SYNCOPE-1662) Leverage MariaDB JSON type
[ https://issues.apache.org/jira/browse/SYNCOPE-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1662: Fix Version/s: 3.0.9 (was: 3.0.8) > Leverage MariaDB JSON type > -- > > Key: SYNCOPE-1662 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1662 > Project: Syncope > Issue Type: New Feature > Components: core >Reporter: Francesco Chicchiriccò >Priority: Major > Labels: jpa, mariadb, persistence > Fix For: 3.0.9, 4.0.0 > > > Similar to SYNCOPE-1395 for PostgreSQL and SYNCOPE-1401 for MySQL, enhance > the JPA layer by empowering [MariaDB JSON > datatype|https://mariadb.com/kb/en/json-data-type/] for user, group and any > object attributes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1621) Allow export for individual items in XML
[ https://issues.apache.org/jira/browse/SYNCOPE-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1621: Fix Version/s: 3.0.9 (was: 3.0.8) > Allow export for individual items in XML > - > > Key: SYNCOPE-1621 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1621 > Project: Syncope > Issue Type: Improvement > Components: console, core >Reporter: Andrea Patricelli >Priority: Major > Fix For: 3.0.9, 4.0.0 > > > Provide a functionality in the admin console (and from REST) that allows one > to view the XML configuration of an individual item. For example, an user > would be interested in seeing the XML representation of the new configuration > parameter, or it might be a user object, group, provisioning rules, etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1823) SCIM: support search by extension attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1823. - Resolution: Fixed > SCIM: support search by extension attributes > > > Key: SYNCOPE-1823 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1823 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Labels: scim > Fix For: 3.0.8, 4.0.0 > > > Per [RFC 7643 section 3.3|https://tools.ietf.org/html/rfc7643#section-3.3], > "Except for the base object schema, the schema extension URI SHALL be used as > a JSON container to distinguish attributes belonging to the extension > namespace from base schema attributes.". See also the example User JSON in > [section 8.3|https://tools.ietf.org/html/rfc7643#section-8.3]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1823) SCIM: support search by extension attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866422#comment-17866422 ] ASF subversion and git services commented on SYNCOPE-1823: -- Commit b69ecb26fe20c7be64ea0949c7b478d97df4e620 in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=b69ecb26fe ] [SYNCOPE-1823] Polishing and adding more tests > SCIM: support search by extension attributes > > > Key: SYNCOPE-1823 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1823 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Labels: scim > Fix For: 3.0.8, 4.0.0 > > > Per [RFC 7643 section 3.3|https://tools.ietf.org/html/rfc7643#section-3.3], > "Except for the base object schema, the schema extension URI SHALL be used as > a JSON container to distinguish attributes belonging to the extension > namespace from base schema attributes.". See also the example User JSON in > [section 8.3|https://tools.ietf.org/html/rfc7643#section-8.3]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1823) SCIM: support search by extension attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866421#comment-17866421 ] ASF subversion and git services commented on SYNCOPE-1823: -- Commit e716cfbdb940ddefc9144dbbe3693c55c47b4103 in syncope's branch refs/heads/3_0_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=e716cfbdb9 ] [SYNCOPE-1823] Polishing and adding more tests > SCIM: support search by extension attributes > > > Key: SYNCOPE-1823 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1823 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Labels: scim > Fix For: 3.0.8, 4.0.0 > > > Per [RFC 7643 section 3.3|https://tools.ietf.org/html/rfc7643#section-3.3], > "Except for the base object schema, the schema extension URI SHALL be used as > a JSON container to distinguish attributes belonging to the extension > namespace from base schema attributes.". See also the example User JSON in > [section 8.3|https://tools.ietf.org/html/rfc7643#section-8.3]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1823) SCIM: support search by extension attributes
Francesco Chicchiriccò created SYNCOPE-1823: --- Summary: SCIM: support search by extension attributes Key: SYNCOPE-1823 URL: https://issues.apache.org/jira/browse/SYNCOPE-1823 Project: Syncope Issue Type: Improvement Components: core Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 3.0.8, 4.0.0 Per [RFC 7643 section 3.3|https://tools.ietf.org/html/rfc7643#section-3.3], "Except for the base object schema, the schema extension URI SHALL be used as a JSON container to distinguish attributes belonging to the extension namespace from base schema attributes.". See also the example User JSON in [section 8.3|https://tools.ietf.org/html/rfc7643#section-8.3]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1822) SCIM: support user extension
[
https://issues.apache.org/jira/browse/SYNCOPE-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863682#comment-17863682
]
ASF subversion and git services commented on SYNCOPE-1822:
--
Commit 9586721892f761b2a7b5a73287f16d073a4ab5de in syncope's branch
refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=9586721892 ]
[SYNCOPE-1822] Prevent NPE
> SCIM: support user extension
>
>
> Key: SYNCOPE-1822
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1822
> Project: Syncope
> Issue Type: Improvement
> Components: documentation, extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Samuel Garofalo
>Priority: Major
> Labels: scim
> Fix For: 3.0.8, 4.0.0
>
>
> Syncope currently allows to manage JSON payloads as follows:
> {code:java}
> {
> "schemas":
> ["urn:ietf:params:scim:schemas:core:2.0:User",
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
> "id": "2819c223-7f76-453a-919d-413861904646",
> "externalId": "701984",
> "userName": "bjen...@example.com",
> ...
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
> "employeeNumber": "701984",
> ...
> }
> }
> {code}
> by mapping all attributes from the SCIM 2.0 specs to Syncope schemas.
> Enterprise User, in particular, is a standard SCIM 2.0 extension with
> [well-defined attributes|https://www.rfc-editor.org/rfc/rfc7643#section-4.3].
> We want to enable Syncope to allow JSON payloads as follows:
> {code:java}
> {
> "schemas":
> ["urn:ietf:params:scim:schemas:core:2.0:User",
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
> "urn:ietf:params:scim:schemas:extension:syncope:2.0:User"],
> "id": "2819c223-7f76-453a-919d-413861904646",
> "externalId": "701984",
> "userName": "bjen...@example.com",
> ...
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
> "employeeNumber": "701984",
> ...
> }
> "urn:ietf:params:scim:schemas:extension:syncope:2.0:User": {
> "myfancyparam": "my fancy value",
> ...
> }
> }
> {code}
> In this way, one can add as many custom attributes as needed, via the
> {{urn:ietf:params:scim:schemas:extension:syncope:2.0:User}} SCIM 2.0
> extension.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1822) SCIM: support user extension
[
https://issues.apache.org/jira/browse/SYNCOPE-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863681#comment-17863681
]
ASF subversion and git services commented on SYNCOPE-1822:
--
Commit 7255d4793aa4cfab02634664ea59ed66a02be240 in syncope's branch
refs/heads/3_0_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=7255d4793a ]
[SYNCOPE-1822] Prevent NPE
> SCIM: support user extension
>
>
> Key: SYNCOPE-1822
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1822
> Project: Syncope
> Issue Type: Improvement
> Components: documentation, extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Samuel Garofalo
>Priority: Major
> Labels: scim
> Fix For: 3.0.8, 4.0.0
>
>
> Syncope currently allows to manage JSON payloads as follows:
> {code:java}
> {
> "schemas":
> ["urn:ietf:params:scim:schemas:core:2.0:User",
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
> "id": "2819c223-7f76-453a-919d-413861904646",
> "externalId": "701984",
> "userName": "bjen...@example.com",
> ...
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
> "employeeNumber": "701984",
> ...
> }
> }
> {code}
> by mapping all attributes from the SCIM 2.0 specs to Syncope schemas.
> Enterprise User, in particular, is a standard SCIM 2.0 extension with
> [well-defined attributes|https://www.rfc-editor.org/rfc/rfc7643#section-4.3].
> We want to enable Syncope to allow JSON payloads as follows:
> {code:java}
> {
> "schemas":
> ["urn:ietf:params:scim:schemas:core:2.0:User",
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
> "urn:ietf:params:scim:schemas:extension:syncope:2.0:User"],
> "id": "2819c223-7f76-453a-919d-413861904646",
> "externalId": "701984",
> "userName": "bjen...@example.com",
> ...
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
> "employeeNumber": "701984",
> ...
> }
> "urn:ietf:params:scim:schemas:extension:syncope:2.0:User": {
> "myfancyparam": "my fancy value",
> ...
> }
> }
> {code}
> In this way, one can add as many custom attributes as needed, via the
> {{urn:ietf:params:scim:schemas:extension:syncope:2.0:User}} SCIM 2.0
> extension.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1822) SCIM: support user extension
[
https://issues.apache.org/jira/browse/SYNCOPE-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samuel Garofalo resolved SYNCOPE-1822.
--
Resolution: Fixed
> SCIM: support user extension
>
>
> Key: SYNCOPE-1822
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1822
> Project: Syncope
> Issue Type: Improvement
> Components: documentation, extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Samuel Garofalo
>Priority: Major
> Labels: scim
> Fix For: 3.0.8, 4.0.0
>
>
> Syncope currently allows to manage JSON payloads as follows:
> {code:java}
> {
> "schemas":
> ["urn:ietf:params:scim:schemas:core:2.0:User",
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
> "id": "2819c223-7f76-453a-919d-413861904646",
> "externalId": "701984",
> "userName": "bjen...@example.com",
> ...
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
> "employeeNumber": "701984",
> ...
> }
> }
> {code}
> by mapping all attributes from the SCIM 2.0 specs to Syncope schemas.
> Enterprise User, in particular, is a standard SCIM 2.0 extension with
> [well-defined attributes|https://www.rfc-editor.org/rfc/rfc7643#section-4.3].
> We want to enable Syncope to allow JSON payloads as follows:
> {code:java}
> {
> "schemas":
> ["urn:ietf:params:scim:schemas:core:2.0:User",
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
> "urn:ietf:params:scim:schemas:extension:syncope:2.0:User"],
> "id": "2819c223-7f76-453a-919d-413861904646",
> "externalId": "701984",
> "userName": "bjen...@example.com",
> ...
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
> "employeeNumber": "701984",
> ...
> }
> "urn:ietf:params:scim:schemas:extension:syncope:2.0:User": {
> "myfancyparam": "my fancy value",
> ...
> }
> }
> {code}
> In this way, one can add as many custom attributes as needed, via the
> {{urn:ietf:params:scim:schemas:extension:syncope:2.0:User}} SCIM 2.0
> extension.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1822) SCIM: support user extension
[
https://issues.apache.org/jira/browse/SYNCOPE-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862796#comment-17862796
]
ASF subversion and git services commented on SYNCOPE-1822:
--
Commit 49fd6223cd6502be8f1c18a5ee41674072e4b29b in syncope's branch
refs/heads/master from Samuel Garofalo
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=49fd6223cd ]
[SYNCOPE-1822] added support for SCIM user extension (#773)
> SCIM: support user extension
>
>
> Key: SYNCOPE-1822
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1822
> Project: Syncope
> Issue Type: Improvement
> Components: documentation, extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Samuel Garofalo
>Priority: Major
> Labels: scim
> Fix For: 3.0.8, 4.0.0
>
>
> Syncope currently allows to manage JSON payloads as follows:
> {code:java}
> {
> "schemas":
> ["urn:ietf:params:scim:schemas:core:2.0:User",
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
> "id": "2819c223-7f76-453a-919d-413861904646",
> "externalId": "701984",
> "userName": "bjen...@example.com",
> ...
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
> "employeeNumber": "701984",
> ...
> }
> }
> {code}
> by mapping all attributes from the SCIM 2.0 specs to Syncope schemas.
> Enterprise User, in particular, is a standard SCIM 2.0 extension with
> [well-defined attributes|https://www.rfc-editor.org/rfc/rfc7643#section-4.3].
> We want to enable Syncope to allow JSON payloads as follows:
> {code:java}
> {
> "schemas":
> ["urn:ietf:params:scim:schemas:core:2.0:User",
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
> "urn:ietf:params:scim:schemas:extension:syncope:2.0:User"],
> "id": "2819c223-7f76-453a-919d-413861904646",
> "externalId": "701984",
> "userName": "bjen...@example.com",
> ...
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
> "employeeNumber": "701984",
> ...
> }
> "urn:ietf:params:scim:schemas:extension:syncope:2.0:User": {
> "myfancyparam": "my fancy value",
> ...
> }
> }
> {code}
> In this way, one can add as many custom attributes as needed, via the
> {{urn:ietf:params:scim:schemas:extension:syncope:2.0:User}} SCIM 2.0
> extension.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1822) SCIM: support user extension
[
https://issues.apache.org/jira/browse/SYNCOPE-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862754#comment-17862754
]
ASF subversion and git services commented on SYNCOPE-1822:
--
Commit d36f208dd1b9e2c2daae5e64a892e5c85b5a2c37 in syncope's branch
refs/heads/3_0_X from Samuel Garofalo
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=d36f208dd1 ]
[SYNCOPE-1822] added support for SCIM user extension (#769)
> SCIM: support user extension
>
>
> Key: SYNCOPE-1822
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1822
> Project: Syncope
> Issue Type: Improvement
> Components: documentation, extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Samuel Garofalo
>Priority: Major
> Labels: scim
> Fix For: 3.0.8, 4.0.0
>
>
> Syncope currently allows to manage JSON payloads as follows:
> {code:java}
> {
> "schemas":
> ["urn:ietf:params:scim:schemas:core:2.0:User",
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
> "id": "2819c223-7f76-453a-919d-413861904646",
> "externalId": "701984",
> "userName": "bjen...@example.com",
> ...
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
> "employeeNumber": "701984",
> ...
> }
> }
> {code}
> by mapping all attributes from the SCIM 2.0 specs to Syncope schemas.
> Enterprise User, in particular, is a standard SCIM 2.0 extension with
> [well-defined attributes|https://www.rfc-editor.org/rfc/rfc7643#section-4.3].
> We want to enable Syncope to allow JSON payloads as follows:
> {code:java}
> {
> "schemas":
> ["urn:ietf:params:scim:schemas:core:2.0:User",
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
> "urn:ietf:params:scim:schemas:extension:syncope:2.0:User"],
> "id": "2819c223-7f76-453a-919d-413861904646",
> "externalId": "701984",
> "userName": "bjen...@example.com",
> ...
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
> "employeeNumber": "701984",
> ...
> }
> "urn:ietf:params:scim:schemas:extension:syncope:2.0:User": {
> "myfancyparam": "my fancy value",
> ...
> }
> }
> {code}
> In this way, one can add as many custom attributes as needed, via the
> {{urn:ietf:params:scim:schemas:extension:syncope:2.0:User}} SCIM 2.0
> extension.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (SYNCOPE-1822) SCIM: support user extension
[
https://issues.apache.org/jira/browse/SYNCOPE-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samuel Garofalo reassigned SYNCOPE-1822:
Assignee: Samuel Garofalo
> SCIM: support user extension
>
>
> Key: SYNCOPE-1822
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1822
> Project: Syncope
> Issue Type: Improvement
> Components: documentation, extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Samuel Garofalo
>Priority: Major
> Labels: scim
> Fix For: 3.0.8, 4.0.0
>
>
> Syncope currently allows to manage JSON payloads as follows:
> {code:java}
> {
> "schemas":
> ["urn:ietf:params:scim:schemas:core:2.0:User",
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
> "id": "2819c223-7f76-453a-919d-413861904646",
> "externalId": "701984",
> "userName": "bjen...@example.com",
> ...
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
> "employeeNumber": "701984",
> ...
> }
> }
> {code}
> by mapping all attributes from the SCIM 2.0 specs to Syncope schemas.
> Enterprise User, in particular, is a standard SCIM 2.0 extension with
> [well-defined attributes|https://www.rfc-editor.org/rfc/rfc7643#section-4.3].
> We want to enable Syncope to allow JSON payloads as follows:
> {code:java}
> {
> "schemas":
> ["urn:ietf:params:scim:schemas:core:2.0:User",
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
> "urn:ietf:params:scim:schemas:extension:syncope:2.0:User"],
> "id": "2819c223-7f76-453a-919d-413861904646",
> "externalId": "701984",
> "userName": "bjen...@example.com",
> ...
> "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
> "employeeNumber": "701984",
> ...
> }
> "urn:ietf:params:scim:schemas:extension:syncope:2.0:User": {
> "myfancyparam": "my fancy value",
> ...
> }
> }
> {code}
> In this way, one can add as many custom attributes as needed, via the
> {{urn:ietf:params:scim:schemas:extension:syncope:2.0:User}} SCIM 2.0
> extension.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1821) Dropdown plain schema type
[
https://issues.apache.org/jira/browse/SYNCOPE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-1821.
-
Resolution: Fixed
> Dropdown plain schema type
> --
>
> Key: SYNCOPE-1821
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1821
> Project: Syncope
> Issue Type: New Feature
> Components: console, core, documentation, enduser
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 4.0.0
>
>
> Introduce a new type for plain schemas: similar to {{Enum}} but with
> available choices computed from a new {{Implementation}} type, rather than
> statically given at definition time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1821) Dropdown plain schema type
[
https://issues.apache.org/jira/browse/SYNCOPE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859972#comment-17859972
]
ASF subversion and git services commented on SYNCOPE-1821:
--
Commit 99777f0b3f935d4518ad8a3b4802cb266f2114e6 in syncope's branch
refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=99777f0b3f ]
[SYNCOPE-1821] Dropdown plain schema type (#759)
> Dropdown plain schema type
> --
>
> Key: SYNCOPE-1821
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1821
> Project: Syncope
> Issue Type: New Feature
> Components: console, core, documentation, enduser
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 4.0.0
>
>
> Introduce a new type for plain schemas: similar to {{Enum}} but with
> available choices computed from a new {{Implementation}} type, rather than
> statically given at definition time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SYNCOPE-1822) SCIM: support user extension
Francesco Chicchiriccò created SYNCOPE-1822:
---
Summary: SCIM: support user extension
Key: SYNCOPE-1822
URL: https://issues.apache.org/jira/browse/SYNCOPE-1822
Project: Syncope
Issue Type: Improvement
Components: documentation, extensions
Reporter: Francesco Chicchiriccò
Fix For: 3.0.8, 4.0.0
Syncope currently allows to manage JSON payloads as follows:
{code:java}
{
"schemas":
["urn:ietf:params:scim:schemas:core:2.0:User",
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
"id": "2819c223-7f76-453a-919d-413861904646",
"externalId": "701984",
"userName": "bjen...@example.com",
...
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
"employeeNumber": "701984",
...
}
}
{code}
by mapping all attributes from the SCIM 2.0 specs to Syncope schemas.
Enterprise User, in particular, is a standard SCIM 2.0 extension with
[well-defined attributes|https://www.rfc-editor.org/rfc/rfc7643#section-4.3].
We want to enable Syncope to allow JSON payloads as follows:
{code:java}
{
"schemas":
["urn:ietf:params:scim:schemas:core:2.0:User",
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
"urn:ietf:params:scim:schemas:extension:syncope:2.0:User"],
"id": "2819c223-7f76-453a-919d-413861904646",
"externalId": "701984",
"userName": "bjen...@example.com",
...
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
"employeeNumber": "701984",
...
}
"urn:ietf:params:scim:schemas:extension:syncope:2.0:User": {
"myfancyparam": "my fancy value",
...
}
}
{code}
In this way, one can add as many custom attributes as needed, via the
{{urn:ietf:params:scim:schemas:extension:syncope:2.0:User}} SCIM 2.0 extension.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SYNCOPE-1821) Dropdown plain schema type
Francesco Chicchiriccò created SYNCOPE-1821:
---
Summary: Dropdown plain schema type
Key: SYNCOPE-1821
URL: https://issues.apache.org/jira/browse/SYNCOPE-1821
Project: Syncope
Issue Type: New Feature
Components: console, core, documentation, enduser
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
Fix For: 4.0.0
Introduce a new type for plain schemas: similar to {{Enum}} but with available
choices computed from a new {{Implementation}} type, rather than statically
given at definition time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1804) Neo4j for Internal Storage
[ https://issues.apache.org/jira/browse/SYNCOPE-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17854001#comment-17854001 ] ASF subversion and git services commented on SYNCOPE-1804: -- Commit 45d8c5613df8f7629210c4bfd24e2780a2606c31 in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=45d8c5613d ] [SYNCOPE-1804] IT case hardening > Neo4j for Internal Storage > -- > > Key: SYNCOPE-1804 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1804 > Project: Syncope > Issue Type: New Feature > Components: core, docker, documentation >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Labels: neo4j > Fix For: 4.0.0 > > > So far, Core persistence [has been based on > JPA|https://syncope.apache.org/docs/3.0/getting-started.html#internal-storage], > and through this, several DBMS and flavors are supported, including variants > featuring JSON-based columns. > Following Spring Data JPA being introduced by SYNCOPE-1799, it seems feasible > to leverage [Spring Data Neo4j|https://spring.io/projects/spring-data-neo4j] > to provide an alternative, Neo4j-based, persistence layer. > Note on licensing: while Neo4j Community itself [is released under GPL > 3.0|https://neo4j.com/licensing/], the [Neo4j Java > driver|https://github.com/neo4j/neo4j-java-driver] - which will be the only > dependency to be actually added besides Spring's - is released under AL 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1804) Neo4j for Internal Storage
[ https://issues.apache.org/jira/browse/SYNCOPE-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853700#comment-17853700 ] ASF subversion and git services commented on SYNCOPE-1804: -- Commit a9f9d1587dce78556669f5f8574b9c81b4e2d99d in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=a9f9d1587d ] [SYNCOPE-1804] Enabling integration tests (with some hopefully temporary exclusions) (#743) > Neo4j for Internal Storage > -- > > Key: SYNCOPE-1804 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1804 > Project: Syncope > Issue Type: New Feature > Components: core, docker, documentation >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Labels: neo4j > Fix For: 4.0.0 > > > So far, Core persistence [has been based on > JPA|https://syncope.apache.org/docs/3.0/getting-started.html#internal-storage], > and through this, several DBMS and flavors are supported, including variants > featuring JSON-based columns. > Following Spring Data JPA being introduced by SYNCOPE-1799, it seems feasible > to leverage [Spring Data Neo4j|https://spring.io/projects/spring-data-neo4j] > to provide an alternative, Neo4j-based, persistence layer. > Note on licensing: while Neo4j Community itself [is released under GPL > 3.0|https://neo4j.com/licensing/], the [Neo4j Java > driver|https://github.com/neo4j/neo4j-java-driver] - which will be the only > dependency to be actually added besides Spring's - is released under AL 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1758) NullPointer exception at WA refresh time during startup
[
https://issues.apache.org/jira/browse/SYNCOPE-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-1758:
Fix Version/s: 3.0.8
(was: 3.0.7)
> 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
>Priority: Minor
> Fix For: 3.0.8, 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.Default
[jira] [Updated] (SYNCOPE-1662) Leverage MariaDB JSON type
[ https://issues.apache.org/jira/browse/SYNCOPE-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1662: Fix Version/s: 3.0.8 (was: 3.0.7) > Leverage MariaDB JSON type > -- > > Key: SYNCOPE-1662 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1662 > Project: Syncope > Issue Type: New Feature > Components: core >Reporter: Francesco Chicchiriccò >Priority: Major > Labels: jpa, mariadb, persistence > Fix For: 3.0.8, 4.0.0 > > > Similar to SYNCOPE-1395 for PostgreSQL and SYNCOPE-1401 for MySQL, enhance > the JPA layer by empowering [MariaDB JSON > datatype|https://mariadb.com/kb/en/json-data-type/] for user, group and any > object attributes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1621) Allow export for individual items in XML
[ https://issues.apache.org/jira/browse/SYNCOPE-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1621: Fix Version/s: 3.0.8 (was: 3.0.7) > Allow export for individual items in XML > - > > Key: SYNCOPE-1621 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1621 > Project: Syncope > Issue Type: Improvement > Components: console, core >Reporter: Andrea Patricelli >Priority: Major > Fix For: 3.0.8, 4.0.0 > > > Provide a functionality in the admin console (and from REST) that allows one > to view the XML configuration of an individual item. For example, an user > would be interested in seeing the XML representation of the new configuration > parameter, or it might be a user object, group, provisioning rules, etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1815) Macro improvements
[ https://issues.apache.org/jira/browse/SYNCOPE-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846676#comment-17846676 ] ASF subversion and git services commented on SYNCOPE-1815: -- Commit 58f9e1ae831a330096ff6eedd07bf7f0c04213dd in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=58f9e1ae83 ] [SYNCOPE-1815] Further Macro improvements (#713) > Macro improvements > -- > > Key: SYNCOPE-1815 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1815 > Project: Syncope > Issue Type: Improvement > Components: common, console, core, documentation >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > Macro tasks, introduced by SYNCOPE-1697, can benefit of a few improvements: > # allow for the same command to be included multiple times > # optional notification on execution completion > # macro parameters > ## form with field validation and mapping to individual commands' > arguments > ## optional validation logic -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1815) Macro improvements
[ https://issues.apache.org/jira/browse/SYNCOPE-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846645#comment-17846645 ] ASF subversion and git services commented on SYNCOPE-1815: -- Commit fffcd719fcc91d57fa1a92bbae7dbb12f83012f2 in syncope's branch refs/heads/3_0_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=fffcd719fc ] [SYNCOPE-1815] Further Macro improvements (#713) > Macro improvements > -- > > Key: SYNCOPE-1815 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1815 > Project: Syncope > Issue Type: Improvement > Components: common, console, core, documentation >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > Macro tasks, introduced by SYNCOPE-1697, can benefit of a few improvements: > # allow for the same command to be included multiple times > # optional notification on execution completion > # macro parameters > ## form with field validation and mapping to individual commands' > arguments > ## optional validation logic -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1820) Console label not working with multivalue schema
[ https://issues.apache.org/jira/browse/SYNCOPE-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1820. - Resolution: Fixed > Console label not working with multivalue schema > > > Key: SYNCOPE-1820 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1820 > Project: Syncope > Issue Type: Bug > Components: console, enduser >Affects Versions: 3.0.6, 3.0.7, 4.0.0 >Reporter: Lorenzo Di Cola >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > Step to reproduce: > * Create a schema and flag multivalue > * Create a label for the schema just created > * Assign the schema to the anyTypeClasses > * Create the entity with this anyTypeClasses associated > The schema name is not the one in the label but the schema id -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1820) Console label not working with multivalue schema
[ https://issues.apache.org/jira/browse/SYNCOPE-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845027#comment-17845027 ] ASF subversion and git services commented on SYNCOPE-1820: -- Commit 76ea64eacdecdad18fde4fde1faaac54021da022 in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=76ea64eacd ] [SYNCOPE-1820] Ensure to get label if available for multivalue attributes on Console and Enduser > Console label not working with multivalue schema > > > Key: SYNCOPE-1820 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1820 > Project: Syncope > Issue Type: Bug > Components: console, enduser >Affects Versions: 3.0.6, 3.0.7, 4.0.0 >Reporter: Lorenzo Di Cola >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > Step to reproduce: > * Create a schema and flag multivalue > * Create a label for the schema just created > * Assign the schema to the anyTypeClasses > * Create the entity with this anyTypeClasses associated > The schema name is not the one in the label but the schema id -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1820) Console label not working with multivalue schema
[ https://issues.apache.org/jira/browse/SYNCOPE-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845026#comment-17845026 ] ASF subversion and git services commented on SYNCOPE-1820: -- Commit 3f1346e2cdbd315a0ee58873c3b1cc2595875d35 in syncope's branch refs/heads/3_0_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=3f1346e2cd ] [SYNCOPE-1820] Ensure to get label if available for multivalue attributes on Console and Enduser > Console label not working with multivalue schema > > > Key: SYNCOPE-1820 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1820 > Project: Syncope > Issue Type: Bug > Components: console, enduser >Affects Versions: 3.0.6, 3.0.7, 4.0.0 >Reporter: Lorenzo Di Cola >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > Step to reproduce: > * Create a schema and flag multivalue > * Create a label for the schema just created > * Assign the schema to the anyTypeClasses > * Create the entity with this anyTypeClasses associated > The schema name is not the one in the label but the schema id -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SYNCOPE-1820) Console label not working with multivalue schema
[ https://issues.apache.org/jira/browse/SYNCOPE-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-1820: --- Assignee: Francesco Chicchiriccò > Console label not working with multivalue schema > > > Key: SYNCOPE-1820 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1820 > Project: Syncope > Issue Type: Bug > Components: console, enduser >Affects Versions: 3.0.6, 3.0.7, 4.0.0 >Reporter: Lorenzo Di Cola >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > Step to reproduce: > * Create a schema and flag multivalue > * Create a label for the schema just created > * Assign the schema to the anyTypeClasses > * Create the entity with this anyTypeClasses associated > The schema name is not the one in the label but the schema id -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1820) Console label not working with multivalue schema
[ https://issues.apache.org/jira/browse/SYNCOPE-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1820: Component/s: enduser > Console label not working with multivalue schema > > > Key: SYNCOPE-1820 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1820 > Project: Syncope > Issue Type: Bug > Components: console, enduser >Affects Versions: 3.0.6, 3.0.7, 4.0.0 >Reporter: Lorenzo Di Cola >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > Step to reproduce: > * Create a schema and flag multivalue > * Create a label for the schema just created > * Assign the schema to the anyTypeClasses > * Create the entity with this anyTypeClasses associated > The schema name is not the one in the label but the schema id -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1820) Console label not working with multivalue schema
Lorenzo Di Cola created SYNCOPE-1820: Summary: Console label not working with multivalue schema Key: SYNCOPE-1820 URL: https://issues.apache.org/jira/browse/SYNCOPE-1820 Project: Syncope Issue Type: Bug Components: console Affects Versions: 3.0.6, 3.0.7, 4.0.0 Reporter: Lorenzo Di Cola Fix For: 3.0.7, 4.0.0 Step to reproduce: * Create a schema and flag multivalue * Create a label for the schema just created * Assign the schema to the anyTypeClasses * Create the entity with this anyTypeClasses associated The schema name is not the one in the label but the schema id -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1815) Macro improvements
[ https://issues.apache.org/jira/browse/SYNCOPE-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1815. - Resolution: Fixed > Macro improvements > -- > > Key: SYNCOPE-1815 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1815 > Project: Syncope > Issue Type: Improvement > Components: common, console, core, documentation >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > Macro tasks, introduced by SYNCOPE-1697, can benefit of a few improvements: > # allow for the same command to be included multiple times > # optional notification on execution completion > # macro parameters > ## form with field validation and mapping to individual commands' > arguments > ## optional validation logic -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1815) Macro improvements
[ https://issues.apache.org/jira/browse/SYNCOPE-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844668#comment-17844668 ] ASF subversion and git services commented on SYNCOPE-1815: -- Commit 7a5819cb83183c856fd1a0c74abba99f84800e55 in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=7a5819cb83 ] [SYNCOPE-1815] Macro improvements (#696) (#709) > Macro improvements > -- > > Key: SYNCOPE-1815 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1815 > Project: Syncope > Issue Type: Improvement > Components: common, console, core, documentation >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > Macro tasks, introduced by SYNCOPE-1697, can benefit of a few improvements: > # allow for the same command to be included multiple times > # optional notification on execution completion > # macro parameters > ## form with field validation and mapping to individual commands' > arguments > ## optional validation logic -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SYNCOPE-1819) API search of any objects by name returns wrong empty result
[
https://issues.apache.org/jira/browse/SYNCOPE-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò closed SYNCOPE-1819.
---
Resolution: Invalid
If you want to read an any object by name, you should be passing its type as
well: see
https://github.com/apache/syncope/blob/3_0_X/common/idrepo/rest-api/src/main/java/org/apache/syncope/common/rest/api/service/AnyObjectService.java#L80
> API search of any objects by name returns wrong empty result
>
>
> Key: SYNCOPE-1819
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1819
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 3.0.6
>Reporter: Andrea Patricelli
>Priority: Major
>
> Searching any objects by name like this in the playground environment
> {code:java}
> curl -X 'GET' \
>
> 'https://syncope-vm2.apache.org/syncope/rest/anyObjects/Canon%20MF%208030cn' \
> -H 'accept: */*' \
> -H 'X-Syncope-Domain: Master' \
> -H 'Authorization: Basic YWRtaW46cGFzc3dvcmQ='{code}
> returns bad 404 result instead of the any object with name "Canon MF 8030cn".
> Search by key still works and the same issue happens on Json persistence.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1819) API search of any objects by name returns wrong empty result
[
https://issues.apache.org/jira/browse/SYNCOPE-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-1819:
Fix Version/s: (was: 4.0.0)
(was: 3.0.7)
> API search of any objects by name returns wrong empty result
>
>
> Key: SYNCOPE-1819
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1819
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 3.0.6
>Reporter: Andrea Patricelli
>Priority: Major
>
> Searching any objects by name like this in the playground environment
> {code:java}
> curl -X 'GET' \
>
> 'https://syncope-vm2.apache.org/syncope/rest/anyObjects/Canon%20MF%208030cn' \
> -H 'accept: */*' \
> -H 'X-Syncope-Domain: Master' \
> -H 'Authorization: Basic YWRtaW46cGFzc3dvcmQ='{code}
> returns bad 404 result instead of the any object with name "Canon MF 8030cn".
> Search by key still works and the same issue happens on Json persistence.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1819) API search of any objects by name returns wrong empty result
[
https://issues.apache.org/jira/browse/SYNCOPE-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844327#comment-17844327
]
Francesco Chicchiriccò commented on SYNCOPE-1819:
-
The docs of the given REST endpoint do not include passing name values, only
key:
https://github.com/apache/syncope/blob/3_0_X/common/idrepo/rest-api/src/main/java/org/apache/syncope/common/rest/api/service/AnyObjectService.java#L62
> API search of any objects by name returns wrong empty result
>
>
> Key: SYNCOPE-1819
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1819
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 3.0.6
>Reporter: Andrea Patricelli
>Priority: Major
> Fix For: 3.0.7, 4.0.0
>
>
> Searching any objects by name like this in the playground environment
> {code:java}
> curl -X 'GET' \
>
> 'https://syncope-vm2.apache.org/syncope/rest/anyObjects/Canon%20MF%208030cn' \
> -H 'accept: */*' \
> -H 'X-Syncope-Domain: Master' \
> -H 'Authorization: Basic YWRtaW46cGFzc3dvcmQ='{code}
> returns bad 404 result instead of the any object with name "Canon MF 8030cn".
> Search by key still works and the same issue happens on Json persistence.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SYNCOPE-1819) API search of any objects by name returns wrong empty result
Andrea Patricelli created SYNCOPE-1819:
--
Summary: API search of any objects by name returns wrong empty
result
Key: SYNCOPE-1819
URL: https://issues.apache.org/jira/browse/SYNCOPE-1819
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 3.0.6
Reporter: Andrea Patricelli
Fix For: 3.0.7, 4.0.0
Searching any objects by name like this in the playground environment
{code:java}
curl -X 'GET' \
'https://syncope-vm2.apache.org/syncope/rest/anyObjects/Canon%20MF%208030cn' \
-H 'accept: */*' \
-H 'X-Syncope-Domain: Master' \
-H 'Authorization: Basic YWRtaW46cGFzc3dvcmQ='{code}
returns bad 404 result instead of the any object with name "Canon MF 8030cn".
Search by key still works and the same issue happens on Json persistence.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1815) Macro improvements
[ https://issues.apache.org/jira/browse/SYNCOPE-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844314#comment-17844314 ] ASF subversion and git services commented on SYNCOPE-1815: -- Commit 346a08c7c069da30005ecf781f05a356b964f5bc in syncope's branch refs/heads/3_0_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=346a08c7c0 ] [SYNCOPE-1815] Macro improvements (#696) > Macro improvements > -- > > Key: SYNCOPE-1815 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1815 > Project: Syncope > Issue Type: Improvement > Components: common, console, core, documentation >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > Macro tasks, introduced by SYNCOPE-1697, can benefit of a few improvements: > # allow for the same command to be included multiple times > # optional notification on execution completion > # macro parameters > ## form with field validation and mapping to individual commands' > arguments > ## optional validation logic -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1818) Wrong status value propagated to external resources if changed while pulling
[
https://issues.apache.org/jira/browse/SYNCOPE-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Patricelli resolved SYNCOPE-1818.
Resolution: Resolved
> Wrong status value propagated to external resources if changed while pulling
>
>
> Key: SYNCOPE-1818
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1818
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 3.0.6
>Reporter: Andrea Patricelli
>Assignee: Andrea Patricelli
>Priority: Major
> Fix For: 3.0.7, 4.0.0
>
>
> In some specific cases the status of an user on an external resource could
> change remotely. If, simultaneously, some other attribute is changed and a
> propagation is fired the wrong status is propagated on the external resources.
> For example, if an active (on syncope) user on resource-pull changes its
> surname, email and status (set to disabled) and a pull is fired, a
> propagation on some target resources occurs, depending on email and/or
> surname mapping. Propagation status is wrong, for example if pulled
> "disabled" the user is propagated active, i.e. {{__ENABLE__}} attribute is
> set to {{false}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1818) Wrong status value propagated to external resources if changed while pulling
[
https://issues.apache.org/jira/browse/SYNCOPE-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17843771#comment-17843771
]
ASF subversion and git services commented on SYNCOPE-1818:
--
Commit 23f2e24906967955737b2ee0b3c72682d78cff14 in syncope's branch
refs/heads/master from Andrea Patricelli
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=23f2e24906 ]
[SYNCOPE-1818] fixes wrong status propagation while pulling a status update
(#703)
-
Co-authored-by: Francesco Chicchiriccò
> Wrong status value propagated to external resources if changed while pulling
>
>
> Key: SYNCOPE-1818
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1818
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 3.0.6
>Reporter: Andrea Patricelli
>Assignee: Andrea Patricelli
>Priority: Major
> Fix For: 3.0.7, 4.0.0
>
>
> In some specific cases the status of an user on an external resource could
> change remotely. If, simultaneously, some other attribute is changed and a
> propagation is fired the wrong status is propagated on the external resources.
> For example, if an active (on syncope) user on resource-pull changes its
> surname, email and status (set to disabled) and a pull is fired, a
> propagation on some target resources occurs, depending on email and/or
> surname mapping. Propagation status is wrong, for example if pulled
> "disabled" the user is propagated active, i.e. {{__ENABLE__}} attribute is
> set to {{false}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1818) Wrong status value propagated to external resources if changed while pulling
[
https://issues.apache.org/jira/browse/SYNCOPE-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17843395#comment-17843395
]
ASF subversion and git services commented on SYNCOPE-1818:
--
Commit 4f1f43f166b0f95008a860c613b629b5bd1538f5 in syncope's branch
refs/heads/3_0_X from Andrea Patricelli
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=4f1f43f166 ]
[SYNCOPE-1818] fixes wrong status propagation while pulling a status update
(#703)
-
Co-authored-by: Francesco Chicchiriccò
> Wrong status value propagated to external resources if changed while pulling
>
>
> Key: SYNCOPE-1818
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1818
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 3.0.6
>Reporter: Andrea Patricelli
>Assignee: Andrea Patricelli
>Priority: Major
> Fix For: 3.0.7, 4.0.0
>
>
> In some specific cases the status of an user on an external resource could
> change remotely. If, simultaneously, some other attribute is changed and a
> propagation is fired the wrong status is propagated on the external resources.
> For example, if an active (on syncope) user on resource-pull changes its
> surname, email and status (set to disabled) and a pull is fired, a
> propagation on some target resources occurs, depending on email and/or
> surname mapping. Propagation status is wrong, for example if pulled
> "disabled" the user is propagated active, i.e. {{__ENABLE__}} attribute is
> set to {{false}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1818) Wrong status value propagated to external resources if changed while pulling
[
https://issues.apache.org/jira/browse/SYNCOPE-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-1818:
Description:
In some specific cases the status of an user on an external resource could
change remotely. If, simultaneously, some other attribute is changed and a
propagation is fired the wrong status is propagated on the external resources.
For example, if an active (on syncope) user on resource-pull changes its
surname, email and status (set to disabled) and a pull is fired, a propagation
on some target resources occurs, depending on email and/or surname mapping.
Propagation status is wrong, for example if pulled "disabled" the user is
propagated active, i.e. {{__ENABLE__}} attribute is set to {{false}}.
was:
In some specific cases the status of an user on an external resource could
change remotely. If, simultaneously, some other attribute is changed and a
propagation is fired the wrong status is propagated on the external resources.
For example, if an active (on syncope) user on resource-pull changes its
surname, email and status (set to disabled) and a pull is fired, a propagation
on some target resources occurs, depending on email and/or surname mapping.
Propagation status is wrong, for example if pulled "disabled" the user is
propagated active, i.e. `__ENABLE__` attribute is set to `false`.
> Wrong status value propagated to external resources if changed while pulling
>
>
> Key: SYNCOPE-1818
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1818
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 3.0.6
>Reporter: Andrea Patricelli
>Assignee: Andrea Patricelli
>Priority: Major
> Fix For: 3.0.7, 4.0.0
>
>
> In some specific cases the status of an user on an external resource could
> change remotely. If, simultaneously, some other attribute is changed and a
> propagation is fired the wrong status is propagated on the external resources.
> For example, if an active (on syncope) user on resource-pull changes its
> surname, email and status (set to disabled) and a pull is fired, a
> propagation on some target resources occurs, depending on email and/or
> surname mapping. Propagation status is wrong, for example if pulled
> "disabled" the user is propagated active, i.e. {{__ENABLE__}} attribute is
> set to {{false}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (SYNCOPE-1818) Wrong status value propagated to external resources if changed while pulling
[ https://issues.apache.org/jira/browse/SYNCOPE-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli reassigned SYNCOPE-1818: -- Assignee: Andrea Patricelli > Wrong status value propagated to external resources if changed while pulling > > > Key: SYNCOPE-1818 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1818 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.6 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > In some specific cases the status of an user on an external resource could > change remotely. If, simultaneously, some other attribute is changed and a > propagation is fired the wrong status is propagated on the external resources. > For example, if an active (on syncope) user on resource-pull changes its > surname, email and status (set to disabled) and a pull is fired, a > propagation on some target resources occurs, depending on email and/or > surname mapping. Propagation status is wrong, for example if pulled > "disabled" the user is propagated active, i.e. `__ENABLE__` attribute is set > to `false`. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1818) Wrong status value propagated to external resources if changed while pulling
Andrea Patricelli created SYNCOPE-1818: -- Summary: Wrong status value propagated to external resources if changed while pulling Key: SYNCOPE-1818 URL: https://issues.apache.org/jira/browse/SYNCOPE-1818 Project: Syncope Issue Type: Bug Components: core Affects Versions: 3.0.6 Reporter: Andrea Patricelli Fix For: 3.0.7, 4.0.0 In some specific cases the status of an user on an external resource could change remotely. If, simultaneously, some other attribute is changed and a propagation is fired the wrong status is propagated on the external resources. For example, if an active (on syncope) user on resource-pull changes its surname, email and status (set to disabled) and a pull is fired, a propagation on some target resources occurs, depending on email and/or surname mapping. Propagation status is wrong, for example if pulled "disabled" the user is propagated active, i.e. `__ENABLE__` attribute is set to `false`. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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] [Commented] (SYNCOPE-1816) Provide the possibility to add a JcifsSpnegoAuthenticationHandler
[ https://issues.apache.org/jira/browse/SYNCOPE-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840512#comment-17840512 ] ASF subversion and git services commented on SYNCOPE-1816: -- Commit 7475ec83dca1b71cbf06ec30a44aacddae5d6ea2 in syncope's branch refs/heads/master from Fabio Martelli [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=7475ec83dc ] [SYNCOPE-1816] Enables LDAP parameters configuration for SPNEGO authentication module (#699) > 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] [Commented] (SYNCOPE-1816) Provide the possibility to add a JcifsSpnegoAuthenticationHandler
[ https://issues.apache.org/jira/browse/SYNCOPE-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840490#comment-17840490 ] ASF subversion and git services commented on SYNCOPE-1816: -- Commit dd732de5fe9d38f0fec09662d7e15511adf8a850 in syncope's branch refs/heads/3_0_X from Fabio Martelli [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=dd732de5fe ] [SYNCOPE-1816] Enables LDAP parameters configuration for SPNEGO authentication module (#699) > 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] [Commented] (SYNCOPE-1804) Neo4j for Internal Storage
[ https://issues.apache.org/jira/browse/SYNCOPE-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839539#comment-17839539 ] ASF subversion and git services commented on SYNCOPE-1804: -- Commit 7ed16b5859fa707f17e6bc37e2cd858617b5793e in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=7ed16b5859 ] [SYNCOPE-1804] Several improvements for Neo4j (#680) > Neo4j for Internal Storage > -- > > Key: SYNCOPE-1804 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1804 > Project: Syncope > Issue Type: New Feature > Components: core, docker, documentation >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Labels: neo4j > Fix For: 4.0.0 > > > So far, Core persistence [has been based on > JPA|https://syncope.apache.org/docs/3.0/getting-started.html#internal-storage], > and through this, several DBMS and flavors are supported, including variants > featuring JSON-based columns. > Following Spring Data JPA being introduced by SYNCOPE-1799, it seems feasible > to leverage [Spring Data Neo4j|https://spring.io/projects/spring-data-neo4j] > to provide an alternative, Neo4j-based, persistence layer. > Note on licensing: while Neo4j Community itself [is released under GPL > 3.0|https://neo4j.com/licensing/], the [Neo4j Java > driver|https://github.com/neo4j/neo4j-java-driver] - which will be the only > dependency to be actually added besides Spring's - is released under AL 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1816) Provide the possibility to add a JcifsSpnegoAuthenticationHandler
[ https://issues.apache.org/jira/browse/SYNCOPE-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838595#comment-17838595 ] ASF subversion and git services commented on SYNCOPE-1816: -- Commit 2c9e1b54ac232bc9f86bc0742033b22da192b774 in syncope's branch refs/heads/master from fabio [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=2c9e1b54ac ] [SYNCOPE-1816] removes ntlm parameter because not available anymore on CAS 7 > 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] [Commented] (SYNCOPE-1816) Provide the possibility to add a JcifsSpnegoAuthenticationHandler
[ https://issues.apache.org/jira/browse/SYNCOPE-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838594#comment-17838594 ] ASF subversion and git services commented on SYNCOPE-1816: -- Commit 6c7bf91ad8deae696c056c1a4a958215085aa681 in syncope's branch refs/heads/master from Fabio Martelli [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=6c7bf91ad8 ] [SYNCOPE-1816] Provides the possibility to add a JcifsSpnegoAuthenticationHandler (#691) > 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] [Commented] (SYNCOPE-1816) Provide the possibility to add a JcifsSpnegoAuthenticationHandler
[ https://issues.apache.org/jira/browse/SYNCOPE-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838580#comment-17838580 ] ASF subversion and git services commented on SYNCOPE-1816: -- Commit 97b8605519daae5d38a21504c8b5a18e9863d66c in syncope's branch refs/heads/3_0_X from Fabio Martelli [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=97b8605519 ] [SYNCOPE-1816] Provides the possibility to add a JcifsSpnegoAuthenticationHandler (#691) > 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] [Resolved] (SYNCOPE-1817) Standalone: components not available
[ https://issues.apache.org/jira/browse/SYNCOPE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1817. - Resolution: Fixed > Standalone: components not available > > > Key: SYNCOPE-1817 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1817 > Project: Syncope > Issue Type: Bug > Components: standalone >Affects Versions: 3.0.6 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > The following issues were reported against Standalone 3.0.6: > # port 9443: connection closed > # unable to download SAML2SP4UI's SP metadata nor to upload SAML2SP4UI's IdP > metadata -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1817) Standalone: components not available
[ https://issues.apache.org/jira/browse/SYNCOPE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838566#comment-17838566 ] ASF subversion and git services commented on SYNCOPE-1817: -- Commit 669715aa8a53ef1165b961eebf33eee1eaf8902b in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=669715aa8a ] [SYNCOPE-1817] Fixing Standalone > Standalone: components not available > > > Key: SYNCOPE-1817 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1817 > Project: Syncope > Issue Type: Bug > Components: standalone >Affects Versions: 3.0.6 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > The following issues were reported against Standalone 3.0.6: > # port 9443: connection closed > # unable to download SAML2SP4UI's SP metadata nor to upload SAML2SP4UI's IdP > metadata -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1817) Standalone: components not available
[ https://issues.apache.org/jira/browse/SYNCOPE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838564#comment-17838564 ] ASF subversion and git services commented on SYNCOPE-1817: -- Commit bb79240ccef7791d31e8360be087ae7d3b3b2c07 in syncope's branch refs/heads/3_0_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=bb79240cce ] [SYNCOPE-1817] Fixing Standalone > Standalone: components not available > > > Key: SYNCOPE-1817 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1817 > Project: Syncope > Issue Type: Bug > Components: standalone >Affects Versions: 3.0.6 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > The following issues were reported against Standalone 3.0.6: > # port 9443: connection closed > # unable to download SAML2SP4UI's SP metadata nor to upload SAML2SP4UI's IdP > metadata -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1816) Provide the possibility to add a JcifsSpnegoAuthenticationHandler
[ https://issues.apache.org/jira/browse/SYNCOPE-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838540#comment-17838540 ] ASF subversion and git services commented on SYNCOPE-1816: -- Commit 2f973e7c36a009afb3bb5b1be54506aae044e85a in syncope's branch refs/heads/SYNCOPE-1816 from fabio [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=2f973e7c36 ] [SYNCOPE-1816] Provides the possibility to add a JcifsSpnegoAuthenticationHandler > 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] [Updated] (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 ] Francesco Chicchiriccò updated SYNCOPE-1816: Fix Version/s: 4.0.0 > 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-1817) Standalone: components not available
Francesco Chicchiriccò created SYNCOPE-1817: --- Summary: Standalone: components not available Key: SYNCOPE-1817 URL: https://issues.apache.org/jira/browse/SYNCOPE-1817 Project: Syncope Issue Type: Bug Components: standalone Affects Versions: 3.0.6 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 3.0.7, 4.0.0 The following issues were reported against Standalone 3.0.6: # port 9443: connection closed # unable to download SAML2SP4UI's SP metadata nor to upload SAML2SP4UI's IdP metadata -- 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] [Updated] (SYNCOPE-1815) Macro improvements
[ https://issues.apache.org/jira/browse/SYNCOPE-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1815: Description: Macro tasks, introduced by SYNCOPE-1697, can benefit of a few improvements: # allow for the same command to be included multiple times # optional notification on execution completion # macro parameters ## form with field validation and mapping to individual commands' arguments ## optional validation logic was: Macro tasks, introduced by SYCOPE-1697, can benefit of a few improvements: # allow for the same command to be included multiple times # optional notification on execution completion # macro parameters ## form with field validation and mapping to individual commands' arguments ## optional validation logic > Macro improvements > -- > > Key: SYNCOPE-1815 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1815 > Project: Syncope > Issue Type: Improvement > Components: common, console, core, documentation >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > Macro tasks, introduced by SYNCOPE-1697, can benefit of a few improvements: > # allow for the same command to be included multiple times > # optional notification on execution completion > # macro parameters > ## form with field validation and mapping to individual commands' > arguments > ## optional validation logic -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1815) Macro improvements
Francesco Chicchiriccò created SYNCOPE-1815: --- Summary: Macro improvements Key: SYNCOPE-1815 URL: https://issues.apache.org/jira/browse/SYNCOPE-1815 Project: Syncope Issue Type: Improvement Components: common, console, core, documentation Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 3.0.7, 4.0.0 Macro tasks, introduced by SYCOPE-1697, can benefit of a few improvements: # allow for the same command to be included multiple times # optional notification on execution completion # macro parameters ## form with field validation and mapping to individual commands' arguments ## optional validation logic -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1813) Wrong provisioning result shown after batch operation
[ https://issues.apache.org/jira/browse/SYNCOPE-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836545#comment-17836545 ] ASF subversion and git services commented on SYNCOPE-1813: -- Commit 0c32003a60a538d976dcc392aa08c0a2d9aa6831 in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=0c32003a60 ] [SYNCOPE-1813] Ensuring (de)provision results are sorted according to request > Wrong provisioning result shown after batch operation > -- > > Key: SYNCOPE-1813 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1813 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 3.0.6 >Reporter: Andrea Patricelli >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > # Login in console as admin > # Click on user and then manage resources > # Select two or more resources which should go into different propagation > outcomes and then click on the gear to execute a batch operation. E.g. if you > run in embedded mode use ws-target-resource-nopropagation2 and resource-testdb > # Run provision and you'll see the result window with wrong outcome order: > result should be resource-testdb -> FAILURE and > ws-target-resource-nopropagation2 -> NOT_ATTEMPTED. It's the opposite, > instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1813) Wrong provisioning result shown after batch operation
[ https://issues.apache.org/jira/browse/SYNCOPE-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1813. - Resolution: Fixed > Wrong provisioning result shown after batch operation > -- > > Key: SYNCOPE-1813 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1813 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 3.0.6 >Reporter: Andrea Patricelli >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > # Login in console as admin > # Click on user and then manage resources > # Select two or more resources which should go into different propagation > outcomes and then click on the gear to execute a batch operation. E.g. if you > run in embedded mode use ws-target-resource-nopropagation2 and resource-testdb > # Run provision and you'll see the result window with wrong outcome order: > result should be resource-testdb -> FAILURE and > ws-target-resource-nopropagation2 -> NOT_ATTEMPTED. It's the opposite, > instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1813) Wrong provisioning result shown after batch operation
[ https://issues.apache.org/jira/browse/SYNCOPE-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836544#comment-17836544 ] ASF subversion and git services commented on SYNCOPE-1813: -- Commit 389a4189052b998bda4affe01001ef2c04fd1dd0 in syncope's branch refs/heads/3_0_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=389a418905 ] [SYNCOPE-1813] Ensuring (de)provision results are sorted according to request > Wrong provisioning result shown after batch operation > -- > > Key: SYNCOPE-1813 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1813 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 3.0.6 >Reporter: Andrea Patricelli >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > # Login in console as admin > # Click on user and then manage resources > # Select two or more resources which should go into different propagation > outcomes and then click on the gear to execute a batch operation. E.g. if you > run in embedded mode use ws-target-resource-nopropagation2 and resource-testdb > # Run provision and you'll see the result window with wrong outcome order: > result should be resource-testdb -> FAILURE and > ws-target-resource-nopropagation2 -> NOT_ATTEMPTED. It's the opposite, > instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SYNCOPE-1813) Wrong provisioning result shown after batch operation
[ https://issues.apache.org/jira/browse/SYNCOPE-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-1813: --- Assignee: Francesco Chicchiriccò > Wrong provisioning result shown after batch operation > -- > > Key: SYNCOPE-1813 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1813 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 3.0.6 >Reporter: Andrea Patricelli >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > # Login in console as admin > # Click on user and then manage resources > # Select two or more resources which should go into different propagation > outcomes and then click on the gear to execute a batch operation. E.g. if you > run in embedded mode use ws-target-resource-nopropagation2 and resource-testdb > # Run provision and you'll see the result window with wrong outcome order: > result should be resource-testdb -> FAILURE and > ws-target-resource-nopropagation2 -> NOT_ATTEMPTED. It's the opposite, > instead. -- 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] [Created] (SYNCOPE-1813) Wrong provisioning result shown after batch operation
Andrea Patricelli created SYNCOPE-1813: -- Summary: Wrong provisioning result shown after batch operation Key: SYNCOPE-1813 URL: https://issues.apache.org/jira/browse/SYNCOPE-1813 Project: Syncope Issue Type: Bug Components: console Affects Versions: 3.0.6 Reporter: Andrea Patricelli Fix For: 3.0.7, 4.0.0 # Login in console as admin # Click on user and then manage resources # Select two or more resources which should go into different propagation outcomes and then click on the gear to execute a batch operation. E.g. if you run in embedded mode use ws-target-resource-nopropagation2 and resource-testdb # Run provision and you'll see the result window with wrong outcome order: result should be resource-testdb -> FAILURE and ws-target-resource-nopropagation2 -> NOT_ATTEMPTED. It's the opposite, instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1812) Can't perform case-sensitive search using MariaDB
[ https://issues.apache.org/jira/browse/SYNCOPE-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1812. - Resolution: Fixed > Can't perform case-sensitive search using MariaDB > - > > Key: SYNCOPE-1812 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1812 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.6 >Reporter: Samuel Garofalo >Assignee: Samuel Garofalo >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > On MariaDB, by default, searches for nonbinary strings (CHAR, VARCHAR, TEXT) > are always case-insensitive. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1812) Can't perform case-sensitive search using MariaDB
[ https://issues.apache.org/jira/browse/SYNCOPE-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17834151#comment-17834151 ] ASF subversion and git services commented on SYNCOPE-1812: -- Commit 65343231b46a773013bb73fb1077037d17bc3c62 in syncope's branch refs/heads/master from Samuel Garofalo [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=65343231b4 ] [SYNCOPE-1812] Instructions about configuring MariaDB for case-sensitive queries (#673) > Can't perform case-sensitive search using MariaDB > - > > Key: SYNCOPE-1812 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1812 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.6 >Reporter: Samuel Garofalo >Assignee: Samuel Garofalo >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > On MariaDB, by default, searches for nonbinary strings (CHAR, VARCHAR, TEXT) > are always case-insensitive. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1812) Can't perform case-sensitive search using MariaDB
[ https://issues.apache.org/jira/browse/SYNCOPE-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17834150#comment-17834150 ] ASF subversion and git services commented on SYNCOPE-1812: -- Commit 57438b78dc9be155d1bcb96c7e2c69bd563a19d8 in syncope's branch refs/heads/3_0_X from Samuel Garofalo [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=57438b78dc ] [SYNCOPE-1812] Instructions about configuring MariaDB for case-sensitive queries (#673) > Can't perform case-sensitive search using MariaDB > - > > Key: SYNCOPE-1812 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1812 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.6 >Reporter: Samuel Garofalo >Assignee: Samuel Garofalo >Priority: Major > Fix For: 3.0.7, 4.0.0 > > > On MariaDB, by default, searches for nonbinary strings (CHAR, VARCHAR, TEXT) > are always case-insensitive. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1812) Can't perform case-sensitive search using MariaDB
Samuel Garofalo created SYNCOPE-1812: Summary: Can't perform case-sensitive search using MariaDB Key: SYNCOPE-1812 URL: https://issues.apache.org/jira/browse/SYNCOPE-1812 Project: Syncope Issue Type: Bug Components: core Affects Versions: 3.0.6 Reporter: Samuel Garofalo Assignee: Samuel Garofalo Fix For: 3.0.7, 4.0.0 On MariaDB, by default, searches for nonbinary strings (CHAR, VARCHAR, TEXT) are always case-insensitive. -- This message was sent by Atlassian Jira (v8.20.10#820010)
