[jira] [Resolved] (SYNCOPE-1361) Custom audit appender does not work after a restart
[ https://issues.apache.org/jira/browse/SYNCOPE-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-1361. - Resolution: Fixed > Custom audit appender does not work after a restart > --- > > Key: SYNCOPE-1361 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1361 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.10, 2.1.1 >Reporter: fabio martelli >Assignee: fabio martelli >Priority: Major > Fix For: 2.0.11, 2.1.2, 3.0.0 > > > When Syncope restarts defined custom appenders stop working. > In order to have them working again tick/untick in configuration audit > section is required. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1361) Custom audit appender does not work after a restart
[ https://issues.apache.org/jira/browse/SYNCOPE-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604456#comment-16604456 ] ASF subversion and git services commented on SYNCOPE-1361: -- Commit 12330a37dc7311cbfdc9dac47029ace56947e4f1 in syncope's branch refs/heads/master from fmartelli [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=12330a3 ] [SYNCOPE-1361] provides a fix into LoggerLoader > Custom audit appender does not work after a restart > --- > > Key: SYNCOPE-1361 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1361 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.10, 2.1.1 >Reporter: fabio martelli >Assignee: fabio martelli >Priority: Major > Fix For: 2.0.11, 2.1.2, 3.0.0 > > > When Syncope restarts defined custom appenders stop working. > In order to have them working again tick/untick in configuration audit > section is required. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1361) Custom audit appender does not work after a restart
[ https://issues.apache.org/jira/browse/SYNCOPE-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604447#comment-16604447 ] ASF subversion and git services commented on SYNCOPE-1361: -- Commit c06920e2e28ab2985763ee1996e746ece8047ae8 in syncope's branch refs/heads/2_1_X from fmartelli [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=c06920e ] [SYNCOPE-1361] provides a fix into LoggerLoader > Custom audit appender does not work after a restart > --- > > Key: SYNCOPE-1361 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1361 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.10, 2.1.1 >Reporter: fabio martelli >Assignee: fabio martelli >Priority: Major > Fix For: 2.0.11, 2.1.2, 3.0.0 > > > When Syncope restarts defined custom appenders stop working. > In order to have them working again tick/untick in configuration audit > section is required. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1366) Audit events ownership always set to admin user
[
https://issues.apache.org/jira/browse/SYNCOPE-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-1366.
-
Resolution: Fixed
> Audit events ownership always set to admin user
> ---
>
> Key: SYNCOPE-1366
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1366
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.10, 2.1.1
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.0.11, 2.1.2, 3.0.0
>
>
> Regardless of the actual user triggering an audit event, {{admin}} is always
> reported.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1366) Audit events ownership always set to admin user
[
https://issues.apache.org/jira/browse/SYNCOPE-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604430#comment-16604430
]
ASF subversion and git services commented on SYNCOPE-1366:
--
Commit 4918e957a15cbde6d62b36ab50e5d8315d00ef55 in syncope's branch
refs/heads/2_1_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=4918e95 ]
[SYNCOPE-1366] Picking the actual user at the right time
> Audit events ownership always set to admin user
> ---
>
> Key: SYNCOPE-1366
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1366
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.10, 2.1.1
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.0.11, 2.1.2, 3.0.0
>
>
> Regardless of the actual user triggering an audit event, {{admin}} is always
> reported.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1366) Audit events ownership always set to admin user
[
https://issues.apache.org/jira/browse/SYNCOPE-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604429#comment-16604429
]
ASF subversion and git services commented on SYNCOPE-1366:
--
Commit 99074ba9300e595c7e4893787fe0b735913d7ca7 in syncope's branch
refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=99074ba ]
[SYNCOPE-1366] Picking the actual user at the right time
> Audit events ownership always set to admin user
> ---
>
> Key: SYNCOPE-1366
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1366
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.10, 2.1.1
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.0.11, 2.1.2, 3.0.0
>
>
> Regardless of the actual user triggering an audit event, {{admin}} is always
> reported.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1366) Audit events ownership always set to admin user
[
https://issues.apache.org/jira/browse/SYNCOPE-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604431#comment-16604431
]
ASF subversion and git services commented on SYNCOPE-1366:
--
Commit d5ac346976dfbfacb2d0e5aa4d6c604c11e90995 in syncope's branch
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=d5ac346 ]
[SYNCOPE-1366] Picking the actual user at the right time
> Audit events ownership always set to admin user
> ---
>
> Key: SYNCOPE-1366
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1366
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.10, 2.1.1
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.0.11, 2.1.2, 3.0.0
>
>
> Regardless of the actual user triggering an audit event, {{admin}} is always
> reported.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1361) Custom audit appender does not work after a restart
[ https://issues.apache.org/jira/browse/SYNCOPE-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604415#comment-16604415 ] ASF subversion and git services commented on SYNCOPE-1361: -- Commit 382a5a05e0676191d46fd5b31fca29471e67c017 in syncope's branch refs/heads/2_0_X from fmartelli [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=382a5a0 ] [SYNCOPE-1361] provides a fix into LoggerLoader > Custom audit appender does not work after a restart > --- > > Key: SYNCOPE-1361 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1361 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.10, 2.1.1 >Reporter: fabio martelli >Assignee: fabio martelli >Priority: Major > Fix For: 2.0.11, 2.1.2, 3.0.0 > > > When Syncope restarts defined custom appenders stop working. > In order to have them working again tick/untick in configuration audit > section is required. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1366) Audit events ownership always set to admin user
Francesco Chicchiriccò created SYNCOPE-1366:
---
Summary: Audit events ownership always set to admin user
Key: SYNCOPE-1366
URL: https://issues.apache.org/jira/browse/SYNCOPE-1366
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 2.1.1, 2.0.10
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
Fix For: 2.0.11, 2.1.2, 3.0.0
Regardless of the actual user triggering an audit event, {{admin}} is always
reported.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1365) Erorr during retrieve candidate groups for approval process
[ https://issues.apache.org/jira/browse/SYNCOPE-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1365. --- Resolution: Fixed > Erorr during retrieve candidate groups for approval process > --- > > Key: SYNCOPE-1365 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1365 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.1.1 >Reporter: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.1.2, 3.0.0 > > > NullPointer exception during approval process -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1365) Erorr during retrieve candidate groups for approval process
[ https://issues.apache.org/jira/browse/SYNCOPE-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604356#comment-16604356 ] ASF subversion and git services commented on SYNCOPE-1365: -- Commit 1068667e90c41cb75d5a508d43f953294646c1b6 in syncope's branch refs/heads/master from [~mdisabatino] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=1068667 ] [SYNCOPE-1365] Fix approval process > Erorr during retrieve candidate groups for approval process > --- > > Key: SYNCOPE-1365 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1365 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.1.1 >Reporter: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.1.2, 3.0.0 > > > NullPointer exception during approval process -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1365) Erorr during retrieve candidate groups for approval process
Marco Di Sabatino Di Diodoro created SYNCOPE-1365: - Summary: Erorr during retrieve candidate groups for approval process Key: SYNCOPE-1365 URL: https://issues.apache.org/jira/browse/SYNCOPE-1365 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.1.1 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.1.2, 3.0.0 NullPointer exception during approval process -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1365) Erorr during retrieve candidate groups for approval process
[ https://issues.apache.org/jira/browse/SYNCOPE-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604354#comment-16604354 ] ASF subversion and git services commented on SYNCOPE-1365: -- Commit 272dc9790eb097879266ff938caffecb367e0593 in syncope's branch refs/heads/2_1_X from [~mdisabatino] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=272dc97 ] [SYNCOPE-1365] Fix approval process > Erorr during retrieve candidate groups for approval process > --- > > Key: SYNCOPE-1365 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1365 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.1.1 >Reporter: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.1.2, 3.0.0 > > > NullPointer exception during approval process -- This message was sent by Atlassian JIRA (v7.6.3#76005)
buildbot success in on syncope-2_0_X-docs
The Buildbot has detected a restored build on builder syncope-2_0_X-docs while building . Full details are available at: https://ci.apache.org/builders/syncope-2_0_X-docs/builds/582 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave3_ubuntu Build Reason: The Nightly scheduler named 'syncope20DocsNightly' triggered this build Build Source Stamp: [branch 2_0_X] HEAD Blamelist: Build succeeded! Sincerely, -The Buildbot
[jira] [Resolved] (SYNCOPE-1364) Upgrade tool from 2.0 script error
[
https://issues.apache.org/jira/browse/SYNCOPE-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-1364.
-
Resolution: Fixed
Thanks for reporting; the problem is now fixed.
2_1_X: https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=38dc035
master: https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=8ebd80a
> Upgrade tool from 2.0 script error
> --
>
> Key: SYNCOPE-1364
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1364
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.1.1
>Reporter: Filipe Silva
>Assignee: Francesco Chicchiriccò
>Priority: Blocker
> Fix For: 2.1.2, 3.0.0
>
>
> The upgrade.sql file generated with the upgrade tool has a script error:
> wrong column name
> {code:java}
> INSERT INTO RealmAction(task_id,implementation_id) VALUES( ...
> {code}
> and should be
> {code:java}
> INSERT INTO RealmAction(realm_id,implementation_id) VALUES( ...
> {code}
> I think the problem is in
> core/upgrade/src/main/java/org/apache/syncope/core/upgrade/GenerateUpgradeSQL.java
> (line 381)
> {code:java}
> OUT.write("_INSERT_ _INTO_ _RealmAction_(task_id,implementation_id) VALUES("
> {code}
> should be corrected to
> {code:java}
> OUT.write("_INSERT_ _INTO_ _RealmAction_(realm_id,implementation_id) VALUES("
> {code}
> (test with postgres DB)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1234) SyncDelta pre-processing
[ https://issues.apache.org/jira/browse/SYNCOPE-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604294#comment-16604294 ] ASF subversion and git services commented on SYNCOPE-1234: -- Commit 8ebd80aab9b02eecf703d20f5c7b99b9412bbfc6 in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=8ebd80a ] [SYNCOPE-1234] Fixing column name > SyncDelta pre-processing > > > Key: SYNCOPE-1234 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1234 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.7, 2.1.0 > > > ConnId's > [SyncDelta|http://connid.tirasa.net/apidocs/1.4/org/identityconnectors/framework/common/objects/SyncDelta.html] > encapsulates the information about retrieved objects during pull. > The SyncDelta content can be seen then as the real starting point of the pull > process of a certain entry. > Currently, such instances can be modified by several > [PullActions|https://github.com/apache/syncope/blob/2_0_X/core/provisioning-api/src/main/java/org/apache/syncope/core/provisioning/api/pushpull/PullActions.java]' > methods; such option was meant to allow flexibility when dealing with wicked > use cases. > For several scenarios, however, such kind of modification occurs too much > later in the process: we need to extract and separate the SyncDelta > pre-processing into a dedicated PullActions' method, to be invoked at the > very beginning. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1234) SyncDelta pre-processing
[ https://issues.apache.org/jira/browse/SYNCOPE-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604293#comment-16604293 ] ASF subversion and git services commented on SYNCOPE-1234: -- Commit 38dc035f17f3611a6ba53d194c949b0decaf3de7 in syncope's branch refs/heads/2_1_X from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=38dc035 ] [SYNCOPE-1234] Fixing column name > SyncDelta pre-processing > > > Key: SYNCOPE-1234 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1234 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.7, 2.1.0 > > > ConnId's > [SyncDelta|http://connid.tirasa.net/apidocs/1.4/org/identityconnectors/framework/common/objects/SyncDelta.html] > encapsulates the information about retrieved objects during pull. > The SyncDelta content can be seen then as the real starting point of the pull > process of a certain entry. > Currently, such instances can be modified by several > [PullActions|https://github.com/apache/syncope/blob/2_0_X/core/provisioning-api/src/main/java/org/apache/syncope/core/provisioning/api/pushpull/PullActions.java]' > methods; such option was meant to allow flexibility when dealing with wicked > use cases. > For several scenarios, however, such kind of modification occurs too much > later in the process: we need to extract and separate the SyncDelta > pre-processing into a dedicated PullActions' method, to be invoked at the > very beginning. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1364) Upgrade tool from 2.0 script error
[
https://issues.apache.org/jira/browse/SYNCOPE-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò reassigned SYNCOPE-1364:
---
Assignee: Francesco Chicchiriccò
> Upgrade tool from 2.0 script error
> --
>
> Key: SYNCOPE-1364
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1364
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.1.1
>Reporter: Filipe Silva
>Assignee: Francesco Chicchiriccò
>Priority: Blocker
> Fix For: 2.1.2, 3.0.0
>
>
> The upgrade.sql file generated with the upgrade tool has a script error:
> wrong column name
> {code:java}
> INSERT INTO RealmAction(task_id,implementation_id) VALUES( ...
> {code}
> and should be
> {code:java}
> INSERT INTO RealmAction(realm_id,implementation_id) VALUES( ...
> {code}
> I think the problem is in
> core/upgrade/src/main/java/org/apache/syncope/core/upgrade/GenerateUpgradeSQL.java
> (line 381)
> {code:java}
> OUT.write("_INSERT_ _INTO_ _RealmAction_(task_id,implementation_id) VALUES("
> {code}
> should be corrected to
> {code:java}
> OUT.write("_INSERT_ _INTO_ _RealmAction_(realm_id,implementation_id) VALUES("
> {code}
> (test with postgres DB)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SYNCOPE-1364) Upgrade tool from 2.0 script error
[
https://issues.apache.org/jira/browse/SYNCOPE-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-1364:
Fix Version/s: 3.0.0
2.1.2
> Upgrade tool from 2.0 script error
> --
>
> Key: SYNCOPE-1364
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1364
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.1.1
>Reporter: Filipe Silva
>Assignee: Francesco Chicchiriccò
>Priority: Blocker
> Fix For: 2.1.2, 3.0.0
>
>
> The upgrade.sql file generated with the upgrade tool has a script error:
> wrong column name
> {code:java}
> INSERT INTO RealmAction(task_id,implementation_id) VALUES( ...
> {code}
> and should be
> {code:java}
> INSERT INTO RealmAction(realm_id,implementation_id) VALUES( ...
> {code}
> I think the problem is in
> core/upgrade/src/main/java/org/apache/syncope/core/upgrade/GenerateUpgradeSQL.java
> (line 381)
> {code:java}
> OUT.write("_INSERT_ _INTO_ _RealmAction_(task_id,implementation_id) VALUES("
> {code}
> should be corrected to
> {code:java}
> OUT.write("_INSERT_ _INTO_ _RealmAction_(realm_id,implementation_id) VALUES("
> {code}
> (test with postgres DB)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SYNCOPE-1364) Upgrade tool from 2.0 script error
Filipe Silva created SYNCOPE-1364:
-
Summary: Upgrade tool from 2.0 script error
Key: SYNCOPE-1364
URL: https://issues.apache.org/jira/browse/SYNCOPE-1364
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 2.1.1
Reporter: Filipe Silva
The upgrade.sql file generated with the upgrade tool has a script error: wrong
column name
{code:java}
INSERT INTO RealmAction(task_id,implementation_id) VALUES( ...
{code}
and should be
{code:java}
INSERT INTO RealmAction(realm_id,implementation_id) VALUES( ...
{code}
I think the problem is in
core/upgrade/src/main/java/org/apache/syncope/core/upgrade/GenerateUpgradeSQL.java
(line 381)
{code:java}
OUT.write("_INSERT_ _INTO_ _RealmAction_(task_id,implementation_id) VALUES("
{code}
should be corrected to
{code:java}
OUT.write("_INSERT_ _INTO_ _RealmAction_(realm_id,implementation_id) VALUES("
{code}
(test with postgres DB)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1361) Custom audit appender does not work after a restart
[ https://issues.apache.org/jira/browse/SYNCOPE-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli reassigned SYNCOPE-1361: --- Assignee: fabio martelli > Custom audit appender does not work after a restart > --- > > Key: SYNCOPE-1361 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1361 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.10, 2.1.1 >Reporter: fabio martelli >Assignee: fabio martelli >Priority: Major > Fix For: 2.0.11, 2.1.2, 3.0.0 > > > When Syncope restarts defined custom appenders stop working. > In order to have them working again tick/untick in configuration audit > section is required. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1363) Deleting multiple users at once reports "Operation delete not supported"
[ https://issues.apache.org/jira/browse/SYNCOPE-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604050#comment-16604050 ] ASF subversion and git services commented on SYNCOPE-1363: -- Commit 63371f7b9fe483dc60c3aaf29c9dde9eb15ecf74 in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=63371f7 ] [SYNCOPE-1363] Avoid re-reading deleted users, groups or any objects > Deleting multiple users at once reports "Operation delete not supported" > > > Key: SYNCOPE-1363 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1363 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.1.1 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Minor > Fix For: 2.1.2, 3.0.0 > > > From Admin Console, select one or more user's checkbox, then click the gear > on the left bottom and finally the delete button: the selected users will be > correctly removed, but an error will be also displayed: "Operation delete not > supported". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1363) Deleting multiple users at once reports "Operation delete not supported"
[ https://issues.apache.org/jira/browse/SYNCOPE-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1363. - Resolution: Fixed > Deleting multiple users at once reports "Operation delete not supported" > > > Key: SYNCOPE-1363 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1363 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.1.1 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Minor > Fix For: 2.1.2, 3.0.0 > > > From Admin Console, select one or more user's checkbox, then click the gear > on the left bottom and finally the delete button: the selected users will be > correctly removed, but an error will be also displayed: "Operation delete not > supported". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1363) Deleting multiple users at once reports "Operation delete not supported"
[ https://issues.apache.org/jira/browse/SYNCOPE-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604049#comment-16604049 ] ASF subversion and git services commented on SYNCOPE-1363: -- Commit 212705fd41435bb99f892c2af5f4a8609e27d1f3 in syncope's branch refs/heads/2_1_X from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=212705f ] [SYNCOPE-1363] Avoid re-reading deleted users, groups or any objects > Deleting multiple users at once reports "Operation delete not supported" > > > Key: SYNCOPE-1363 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1363 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.1.1 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Minor > Fix For: 2.1.2, 3.0.0 > > > From Admin Console, select one or more user's checkbox, then click the gear > on the left bottom and finally the delete button: the selected users will be > correctly removed, but an error will be also displayed: "Operation delete not > supported". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1363) Deleting multiple users at once reports "Operation delete not supported"
Francesco Chicchiriccò created SYNCOPE-1363: --- Summary: Deleting multiple users at once reports "Operation delete not supported" Key: SYNCOPE-1363 URL: https://issues.apache.org/jira/browse/SYNCOPE-1363 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.1.1 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 2.1.2, 3.0.0 >From Admin Console, select one or more user's checkbox, then click the gear on >the left bottom and finally the delete button: the selected users will be >correctly removed, but an error will be also displayed: "Operation delete not >supported". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1220) Support Groovy implementations in the Netbeans IDE plugin
[ https://issues.apache.org/jira/browse/SYNCOPE-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604011#comment-16604011 ] ASF subversion and git services commented on SYNCOPE-1220: -- Commit 0e6ee15026ad24e5c68338507bcee756fe4b44b5 in syncope's branch refs/heads/2_1_X from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=0e6ee15 ] [SYNCOPE-1220] Why hosting duplicates? > Support Groovy implementations in the Netbeans IDE plugin > - > > Key: SYNCOPE-1220 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1220 > Project: Syncope > Issue Type: New Feature > Components: ide >Reporter: Francesco Chicchiriccò >Assignee: Andrea Patricelli >Priority: Major > Labels: gsoc2018, netbeans > Fix For: 2.1.2, 3.0.0 > > Attachments: syncope-ide-netbeans-2.1.0-SNAPSHOT.nbm, > syncope_error.PNG > > > SYNCOPE-956 introduced the possibility to provide Groovy-based > implementations. > The Netbeans IDE plugin should be extended to support this. > This issue basically starts from the work already done for SYNCOPE-808. This > means that there is an already existing netbeans plugin for Syncope. For more > info please see > [this|https://syncope.apache.org/docs/reference-guide.html#netbeans-ide-plugin] > and > [https://syncope.apache.org/docs/getting-started.html#netbeans-ide-plugin] > Please install this plugin and let it work with your local Syncope > installation, in order to understand how it works and interacts with Syncope. > The goal is to improve the current netbeans plugin to create and edit (also > format) Groovy scripts used to extend default Syncope behavior. Refer to > SYNCOPE-956 to have an idea of what I'm talking about. Basically this means > that some default or "open to implementation" functionalities of Syncope Idm > can be improved or developed by pluggin in groovy scripts. This mechanism > allows to develop custom behaviors for Syncope, based on specific project > requirements. > [Here|http://syncope.apache.org/docs/reference-guide.html#customization-core] > is the list of customizable features. > Since [Netbeans > 9|https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Beta] > is near to be released, develop this plugin referring to Netbeans 9 > (currently beta). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1220) Support Groovy implementations in the Netbeans IDE plugin
[ https://issues.apache.org/jira/browse/SYNCOPE-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604012#comment-16604012 ] ASF subversion and git services commented on SYNCOPE-1220: -- Commit 4546c3a54d9678002eac30dced8f916f3317a211 in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=4546c3a ] [SYNCOPE-1220] Why hosting duplicates? > Support Groovy implementations in the Netbeans IDE plugin > - > > Key: SYNCOPE-1220 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1220 > Project: Syncope > Issue Type: New Feature > Components: ide >Reporter: Francesco Chicchiriccò >Assignee: Andrea Patricelli >Priority: Major > Labels: gsoc2018, netbeans > Fix For: 2.1.2, 3.0.0 > > Attachments: syncope-ide-netbeans-2.1.0-SNAPSHOT.nbm, > syncope_error.PNG > > > SYNCOPE-956 introduced the possibility to provide Groovy-based > implementations. > The Netbeans IDE plugin should be extended to support this. > This issue basically starts from the work already done for SYNCOPE-808. This > means that there is an already existing netbeans plugin for Syncope. For more > info please see > [this|https://syncope.apache.org/docs/reference-guide.html#netbeans-ide-plugin] > and > [https://syncope.apache.org/docs/getting-started.html#netbeans-ide-plugin] > Please install this plugin and let it work with your local Syncope > installation, in order to understand how it works and interacts with Syncope. > The goal is to improve the current netbeans plugin to create and edit (also > format) Groovy scripts used to extend default Syncope behavior. Refer to > SYNCOPE-956 to have an idea of what I'm talking about. Basically this means > that some default or "open to implementation" functionalities of Syncope Idm > can be improved or developed by pluggin in groovy scripts. This mechanism > allows to develop custom behaviors for Syncope, based on specific project > requirements. > [Here|http://syncope.apache.org/docs/reference-guide.html#customization-core] > is the list of customizable features. > Since [Netbeans > 9|https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Beta] > is near to be released, develop this plugin referring to Netbeans 9 > (currently beta). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1362) Sorting users by creation date raises RuntimeException
[ https://issues.apache.org/jira/browse/SYNCOPE-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1362. - Resolution: Fixed > Sorting users by creation date raises RuntimeException > -- > > Key: SYNCOPE-1362 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1362 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.1.1 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.1.2, 3.0.0 > > > When sorting users by their creation date, a full-page stack trace is > reported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1362) Sorting users by creation date raises RuntimeException
[ https://issues.apache.org/jira/browse/SYNCOPE-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603981#comment-16603981 ] ASF subversion and git services commented on SYNCOPE-1362: -- Commit 3a97b618e24173c6cfd4d97341b2d000553f0939 in syncope's branch refs/heads/2_1_X from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=3a97b61 ] [SYNCOPE-1362] Troublesome Optional > Sorting users by creation date raises RuntimeException > -- > > Key: SYNCOPE-1362 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1362 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.1.1 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.1.2, 3.0.0 > > > When sorting users by their creation date, a full-page stack trace is > reported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1362) Sorting users by creation date raises RuntimeException
[ https://issues.apache.org/jira/browse/SYNCOPE-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603982#comment-16603982 ] ASF subversion and git services commented on SYNCOPE-1362: -- Commit d5e73caeebdf5c772ebfd5da958b380c1ec6fd5c in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=d5e73ca ] [SYNCOPE-1362] Troublesome Optional > Sorting users by creation date raises RuntimeException > -- > > Key: SYNCOPE-1362 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1362 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.1.1 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.1.2, 3.0.0 > > > When sorting users by their creation date, a full-page stack trace is > reported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1362) Sorting users by creation date raises RuntimeException
Francesco Chicchiriccò created SYNCOPE-1362: --- Summary: Sorting users by creation date raises RuntimeException Key: SYNCOPE-1362 URL: https://issues.apache.org/jira/browse/SYNCOPE-1362 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.1.1 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 2.1.2, 3.0.0 When sorting users by their creation date, a full-page stack trace is reported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
