[jira] [Commented] (SYNCOPE-1144) Customizable Audit appender

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085853#comment-16085853
 ] 

ASF subversion and git services commented on SYNCOPE-1144:
--

Commit d0284e0dbbeab6423c9d4b7a52990e8b73b64e23 in syncope's branch 
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=d0284e0 ]

[SYNCOPE-1144] Fixing source links


> Customizable Audit appender
> ---
>
> Key: SYNCOPE-1144
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1144
> Project: Syncope
>  Issue Type: New Feature
>  Components: common, console, core
>Reporter: Francesco Chicchiriccò
>Assignee: Andrea Patricelli
> Fix For: 2.0.5, 2.1.0
>
>
> The Audit mechanism is based on LOG4J, configured to use the {{JDBCAppender}} 
> to store the audit statements into the {{SyncopeAudit}} table in the internal 
> storage.
> Besides this base mechanism, we can introduce the {{AuditAppender}} 
> interface, whose instances can:
> # declare which event(s) they will be invoked with
> # declare another LOG4J appender to send the statements to (besides the 
> {{JDBCAppender}} as above)
> # optionally offer the ability to transform the standard statement to a 
> format more suitable to the target appender



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SYNCOPE-1160) When defining the provisioning rules of a resource disable the first Previous button

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-1160:

Description: 
When  defining the provisioning rules of a resource disable the first Previous 
button:
it will go to the "Specify the type of the provisioning object" that should not 
be editable at that time

  was:
When editing a resource disable the first Previous button:
it will go to the "Specify the type of the provisioning object" that should not 
be editable at that time

Summary: When defining the provisioning rules of a resource disable the 
first Previous button  (was: When editing a resource disable the first Previous 
button)

> When defining the provisioning rules of a resource disable the first Previous 
> button
> 
>
> Key: SYNCOPE-1160
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1160
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
>
> When  defining the provisioning rules of a resource disable the first 
> Previous button:
> it will go to the "Specify the type of the provisioning object" that should 
> not be editable at that time



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (SYNCOPE-1162) Change to Connector's display name not reflected by contextual menu

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò resolved SYNCOPE-1162.
-
Resolution: Fixed

> Change to Connector's display name not reflected by contextual menu
> ---
>
> Key: SYNCOPE-1162
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1162
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
>
> In the Topology page, if changing the display name of an existing Connector, 
> the contextual menu keeps showing the previous one until the page is reloaded.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (SYNCOPE-1162) Change to Connector's display name not reflected by contextual menu

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò reassigned SYNCOPE-1162:
---

Assignee: Francesco Chicchiriccò

> Change to Connector's display name not reflected by contextual menu
> ---
>
> Key: SYNCOPE-1162
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1162
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
>
> In the Topology page, if changing the display name of an existing Connector, 
> the contextual menu keeps showing the previous one until the page is reloaded.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1162) Change to Connector's display name not reflected by contextual menu

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085751#comment-16085751
 ] 

ASF subversion and git services commented on SYNCOPE-1162:
--

Commit 22fdeda515d2e01877fd0048aa4a3e235da5d131 in syncope's branch 
refs/heads/2_0_X from [~skylark17]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=22fdeda ]

[SYNCOPE-1162] The changes of Connector's display name is now reflected to 
contextual menu in Admin Console


> Change to Connector's display name not reflected by contextual menu
> ---
>
> Key: SYNCOPE-1162
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1162
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
>
> In the Topology page, if changing the display name of an existing Connector, 
> the contextual menu keeps showing the previous one until the page is reloaded.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1162) Change to Connector's display name not reflected by contextual menu

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085753#comment-16085753
 ] 

ASF GitHub Bot commented on SYNCOPE-1162:
-

Github user asfgit closed the pull request at:

https://github.com/apache/syncope/pull/55


> Change to Connector's display name not reflected by contextual menu
> ---
>
> Key: SYNCOPE-1162
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1162
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
>
> In the Topology page, if changing the display name of an existing Connector, 
> the contextual menu keeps showing the previous one until the page is reloaded.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1162) Change to Connector's display name not reflected by contextual menu

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085752#comment-16085752
 ] 

ASF subversion and git services commented on SYNCOPE-1162:
--

Commit 715745275b0c8993f48d206231aaf0935f94d17b in syncope's branch 
refs/heads/master from [~skylark17]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=7157452 ]

[SYNCOPE-1162] The changes of Connector's display name is now reflected to 
contextual menu in Admin Console - This closes #55


> Change to Connector's display name not reflected by contextual menu
> ---
>
> Key: SYNCOPE-1162
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1162
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
>
> In the Topology page, if changing the display name of an existing Connector, 
> the contextual menu keeps showing the previous one until the page is reloaded.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] syncope pull request #55: [SYNCOPE-1162] The changes of Connector's display ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/syncope/pull/55


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (SYNCOPE-1162) Change to Connector's display name not reflected by contextual menu

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085748#comment-16085748
 ] 

ASF GitHub Bot commented on SYNCOPE-1162:
-

GitHub user mat-ale opened a pull request:

https://github.com/apache/syncope/pull/55

[SYNCOPE-1162] The changes of Connector's display name is now reflected to 
contextual menu in Admin Console

Hi,

this fixes 
[[SYNCOPE-1162]](https://issues.apache.org/jira/browse/SYNCOPE-1162).

Regards,
Matteo


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mat-ale/syncope SYNCOPE-1162

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/syncope/pull/55.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #55


commit 22fdeda515d2e01877fd0048aa4a3e235da5d131
Author: Matteo Alessandroni 
Date:   2017-07-13T14:12:31Z

[SYNCOPE-1162] The changes of Connector's display name is now reflected to 
contextual menu in Admin Console




> Change to Connector's display name not reflected by contextual menu
> ---
>
> Key: SYNCOPE-1162
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1162
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
>
> In the Topology page, if changing the display name of an existing Connector, 
> the contextual menu keeps showing the previous one until the page is reloaded.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] syncope pull request #55: [SYNCOPE-1162] The changes of Connector's display ...

[mat-ale]

GitHub user mat-ale opened a pull request:

https://github.com/apache/syncope/pull/55

[SYNCOPE-1162] The changes of Connector's display name is now reflected to 
contextual menu in Admin Console

Hi,

this fixes 
[[SYNCOPE-1162]](https://issues.apache.org/jira/browse/SYNCOPE-1162).

Regards,
Matteo


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mat-ale/syncope SYNCOPE-1162

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/syncope/pull/55.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #55


commit 22fdeda515d2e01877fd0048aa4a3e235da5d131
Author: Matteo Alessandroni 
Date:   2017-07-13T14:12:31Z

[SYNCOPE-1162] The changes of Connector's display name is now reflected to 
contextual menu in Admin Console




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Assigned] (SYNCOPE-1147) Extend SAML 2.0 IdP mapping to Roles

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò reassigned SYNCOPE-1147:
---

Assignee: Francesco Chicchiriccò

> Extend SAML 2.0 IdP mapping to Roles
> 
>
> Key: SYNCOPE-1147
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1147
> Project: Syncope
>  Issue Type: Improvement
>  Components: extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.5, 2.1.0
>
>
> Extend the current mapping, that can be provided for the supported SAML 2.0 
> IdPs, to define which attribute(s) should be used to assign Roles to the 
> internal Users when logging in via SAML.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (SYNCOPE-1146) On-the-fly creation of unmatched users logging via SAML 2.0

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò reassigned SYNCOPE-1146:
---

Assignee: Francesco Chicchiriccò

> On-the-fly creation of unmatched users logging via SAML 2.0
> ---
>
> Key: SYNCOPE-1146
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1146
> Project: Syncope
>  Issue Type: Improvement
>  Components: extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.5, 2.1.0
>
>
> As per the current implementation, when logging into the Admin Console via 
> SAML 2.0, an internal user matching the configured attribute of the 
> Authentication Assertion is looked up.
> If not found, an error is raised.
> Things could be configured, however, to create on-the-fly an internal user 
> with the attributes provided by the Authentication Assertion, and to let them 
> log in.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1144) Customizable Audit appender

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085740#comment-16085740
 ] 

ASF subversion and git services commented on SYNCOPE-1144:
--

Commit 0ff4d8a4408b1080c4e7f2ad3e600db5d3c59cf5 in syncope's branch 
refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=0ff4d8a ]

[SYNCOPE-1144] Minor changes and cleanup


> Customizable Audit appender
> ---
>
> Key: SYNCOPE-1144
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1144
> Project: Syncope
>  Issue Type: New Feature
>  Components: common, console, core
>Reporter: Francesco Chicchiriccò
>Assignee: Andrea Patricelli
> Fix For: 2.0.5, 2.1.0
>
>
> The Audit mechanism is based on LOG4J, configured to use the {{JDBCAppender}} 
> to store the audit statements into the {{SyncopeAudit}} table in the internal 
> storage.
> Besides this base mechanism, we can introduce the {{AuditAppender}} 
> interface, whose instances can:
> # declare which event(s) they will be invoked with
> # declare another LOG4J appender to send the statements to (besides the 
> {{JDBCAppender}} as above)
> # optionally offer the ability to transform the standard statement to a 
> format more suitable to the target appender



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1144) Customizable Audit appender

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085741#comment-16085741
 ] 

ASF subversion and git services commented on SYNCOPE-1144:
--

Commit cb57c5ad20bcd90efe09d0666f27ab151aa4b00c in syncope's branch 
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=cb57c5a ]

[SYNCOPE-1144] Minor changes and cleanup


> Customizable Audit appender
> ---
>
> Key: SYNCOPE-1144
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1144
> Project: Syncope
>  Issue Type: New Feature
>  Components: common, console, core
>Reporter: Francesco Chicchiriccò
>Assignee: Andrea Patricelli
> Fix For: 2.0.5, 2.1.0
>
>
> The Audit mechanism is based on LOG4J, configured to use the {{JDBCAppender}} 
> to store the audit statements into the {{SyncopeAudit}} table in the internal 
> storage.
> Besides this base mechanism, we can introduce the {{AuditAppender}} 
> interface, whose instances can:
> # declare which event(s) they will be invoked with
> # declare another LOG4J appender to send the statements to (besides the 
> {{JDBCAppender}} as above)
> # optionally offer the ability to transform the standard statement to a 
> format more suitable to the target appender



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1151) Glinch in the root realm information

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085695#comment-16085695
 ] 

ASF GitHub Bot commented on SYNCOPE-1151:
-

Github user mat-ale commented on the issue:

https://github.com/apache/syncope/pull/54
  
Great! You're welcome.


>  Glinch in the root realm information
> -
>
> Key: SYNCOPE-1151
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1151
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_032.png, Selection_033.png
>
>
> A small incoherence in the root real info screen and edit screen:
> Choosing the realms (left side) or choosing the root ( / ) realm gives (see 
> Selection_032.png file)
> !Selection_032.png|thumbnail!
> but after creating an realm "below" the root it gives (see Selection_033.png 
> file)
> !Selection_033.png|thumbnail!
> (I highlight the change)
> I think that the last one is the correct one because that in the only way to 
> in the edit realm screen of the root ( / ) to be able to edit the assigned 
> resources (because it also changes) 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1151) Glinch in the root realm information

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085689#comment-16085689
 ] 

ASF subversion and git services commented on SYNCOPE-1151:
--

Commit d7fbfe4862851bc5d7833dbb293c6b3f4b5185d5 in syncope's branch 
refs/heads/master from [~skylark17]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=d7fbfe4 ]

Realm is correctly loaded after creation for SYNCOPE-1151 - This closes #54


>  Glinch in the root realm information
> -
>
> Key: SYNCOPE-1151
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1151
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_032.png, Selection_033.png
>
>
> A small incoherence in the root real info screen and edit screen:
> Choosing the realms (left side) or choosing the root ( / ) realm gives (see 
> Selection_032.png file)
> !Selection_032.png|thumbnail!
> but after creating an realm "below" the root it gives (see Selection_033.png 
> file)
> !Selection_033.png|thumbnail!
> (I highlight the change)
> I think that the last one is the correct one because that in the only way to 
> in the edit realm screen of the root ( / ) to be able to edit the assigned 
> resources (because it also changes) 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (SYNCOPE-1151) Glinch in the root realm information

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò resolved SYNCOPE-1151.
-
Resolution: Fixed

>  Glinch in the root realm information
> -
>
> Key: SYNCOPE-1151
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1151
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_032.png, Selection_033.png
>
>
> A small incoherence in the root real info screen and edit screen:
> Choosing the realms (left side) or choosing the root ( / ) realm gives (see 
> Selection_032.png file)
> !Selection_032.png|thumbnail!
> but after creating an realm "below" the root it gives (see Selection_033.png 
> file)
> !Selection_033.png|thumbnail!
> (I highlight the change)
> I think that the last one is the correct one because that in the only way to 
> in the edit realm screen of the root ( / ) to be able to edit the assigned 
> resources (because it also changes) 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1151) Glinch in the root realm information

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085690#comment-16085690
 ] 

ASF GitHub Bot commented on SYNCOPE-1151:
-

Github user asfgit closed the pull request at:

https://github.com/apache/syncope/pull/54


>  Glinch in the root realm information
> -
>
> Key: SYNCOPE-1151
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1151
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_032.png, Selection_033.png
>
>
> A small incoherence in the root real info screen and edit screen:
> Choosing the realms (left side) or choosing the root ( / ) realm gives (see 
> Selection_032.png file)
> !Selection_032.png|thumbnail!
> but after creating an realm "below" the root it gives (see Selection_033.png 
> file)
> !Selection_033.png|thumbnail!
> (I highlight the change)
> I think that the last one is the correct one because that in the only way to 
> in the edit realm screen of the root ( / ) to be able to edit the assigned 
> resources (because it also changes) 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1151) Glinch in the root realm information

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085688#comment-16085688
 ] 

ASF subversion and git services commented on SYNCOPE-1151:
--

Commit 38ff9d11fd65181030284a00e585f32b95294507 in syncope's branch 
refs/heads/2_0_X from [~skylark17]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=38ff9d1 ]

Realm is correctly loaded after creation for SYNCOPE-1151


>  Glinch in the root realm information
> -
>
> Key: SYNCOPE-1151
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1151
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_032.png, Selection_033.png
>
>
> A small incoherence in the root real info screen and edit screen:
> Choosing the realms (left side) or choosing the root ( / ) realm gives (see 
> Selection_032.png file)
> !Selection_032.png|thumbnail!
> but after creating an realm "below" the root it gives (see Selection_033.png 
> file)
> !Selection_033.png|thumbnail!
> (I highlight the change)
> I think that the last one is the correct one because that in the only way to 
> in the edit realm screen of the root ( / ) to be able to edit the assigned 
> resources (because it also changes) 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1151) Glinch in the root realm information

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085693#comment-16085693
 ] 

ASF GitHub Bot commented on SYNCOPE-1151:
-

Github user ilgrosso commented on the issue:

https://github.com/apache/syncope/pull/54
  
LGTM just merged, thanks!


>  Glinch in the root realm information
> -
>
> Key: SYNCOPE-1151
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1151
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_032.png, Selection_033.png
>
>
> A small incoherence in the root real info screen and edit screen:
> Choosing the realms (left side) or choosing the root ( / ) realm gives (see 
> Selection_032.png file)
> !Selection_032.png|thumbnail!
> but after creating an realm "below" the root it gives (see Selection_033.png 
> file)
> !Selection_033.png|thumbnail!
> (I highlight the change)
> I think that the last one is the correct one because that in the only way to 
> in the edit realm screen of the root ( / ) to be able to edit the assigned 
> resources (because it also changes) 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] syncope issue #54: Realm is correctly loaded after creation in Admin Console...

[ilgrosso]

Github user ilgrosso commented on the issue:

https://github.com/apache/syncope/pull/54
  
LGTM just merged, thanks!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] syncope pull request #54: Realm is correctly loaded after creation in Admin ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/syncope/pull/54


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Assigned] (SYNCOPE-1151) Glinch in the root realm information

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò reassigned SYNCOPE-1151:
---

Assignee: Francesco Chicchiriccò

>  Glinch in the root realm information
> -
>
> Key: SYNCOPE-1151
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1151
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_032.png, Selection_033.png
>
>
> A small incoherence in the root real info screen and edit screen:
> Choosing the realms (left side) or choosing the root ( / ) realm gives (see 
> Selection_032.png file)
> !Selection_032.png|thumbnail!
> but after creating an realm "below" the root it gives (see Selection_033.png 
> file)
> !Selection_033.png|thumbnail!
> (I highlight the change)
> I think that the last one is the correct one because that in the only way to 
> in the edit realm screen of the root ( / ) to be able to edit the assigned 
> resources (because it also changes) 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1151) Glinch in the root realm information

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085686#comment-16085686
 ] 

ASF GitHub Bot commented on SYNCOPE-1151:
-

GitHub user mat-ale opened a pull request:

https://github.com/apache/syncope/pull/54

Realm is correctly loaded after creation in Admin Console for [SYNCOPE-1151]

Hi,

this fixes 
[[SYNCOPE-1151]](https://issues.apache.org/jira/browse/SYNCOPE-1151).

Regards,
Matteo

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mat-ale/syncope SYNCOPE-1151

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/syncope/pull/54.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #54


commit 0e104cbb65607959e18c9da577030972e2160517
Author: Matteo Alessandroni 
Date:   2017-07-13T13:16:45Z

Realm is correctly loaded after creation for SYNCOPE-1151




>  Glinch in the root realm information
> -
>
> Key: SYNCOPE-1151
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1151
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_032.png, Selection_033.png
>
>
> A small incoherence in the root real info screen and edit screen:
> Choosing the realms (left side) or choosing the root ( / ) realm gives (see 
> Selection_032.png file)
> !Selection_032.png|thumbnail!
> but after creating an realm "below" the root it gives (see Selection_033.png 
> file)
> !Selection_033.png|thumbnail!
> (I highlight the change)
> I think that the last one is the correct one because that in the only way to 
> in the edit realm screen of the root ( / ) to be able to edit the assigned 
> resources (because it also changes) 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] syncope pull request #54: Realm is correctly loaded after creation in Admin ...

[mat-ale]

GitHub user mat-ale opened a pull request:

https://github.com/apache/syncope/pull/54

Realm is correctly loaded after creation in Admin Console for [SYNCOPE-1151]

Hi,

this fixes 
[[SYNCOPE-1151]](https://issues.apache.org/jira/browse/SYNCOPE-1151).

Regards,
Matteo

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mat-ale/syncope SYNCOPE-1151

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/syncope/pull/54.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #54


commit 0e104cbb65607959e18c9da577030972e2160517
Author: Matteo Alessandroni 
Date:   2017-07-13T13:16:45Z

Realm is correctly loaded after creation for SYNCOPE-1151




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Resolved] (SYNCOPE-1144) Customizable Audit appender

[Andrea Patricelli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Patricelli resolved SYNCOPE-1144.

Resolution: Fixed

> Customizable Audit appender
> ---
>
> Key: SYNCOPE-1144
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1144
> Project: Syncope
>  Issue Type: New Feature
>  Components: common, console, core
>Reporter: Francesco Chicchiriccò
>Assignee: Andrea Patricelli
> Fix For: 2.0.5, 2.1.0
>
>
> The Audit mechanism is based on LOG4J, configured to use the {{JDBCAppender}} 
> to store the audit statements into the {{SyncopeAudit}} table in the internal 
> storage.
> Besides this base mechanism, we can introduce the {{AuditAppender}} 
> interface, whose instances can:
> # declare which event(s) they will be invoked with
> # declare another LOG4J appender to send the statements to (besides the 
> {{JDBCAppender}} as above)
> # optionally offer the ability to transform the standard statement to a 
> format more suitable to the target appender



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1144) Customizable Audit appender

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085630#comment-16085630
 ] 

ASF subversion and git services commented on SYNCOPE-1144:
--

Commit dc4b83ef1cbf76240bf24c9b8a7e8cc9ae0a9994 in syncope's branch 
refs/heads/2_0_X from [~andrea.patricelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=dc4b83e ]

[SYNCOPE-1144] configurable audit appenders with message rewrite option


> Customizable Audit appender
> ---
>
> Key: SYNCOPE-1144
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1144
> Project: Syncope
>  Issue Type: New Feature
>  Components: common, console, core
>Reporter: Francesco Chicchiriccò
>Assignee: Andrea Patricelli
> Fix For: 2.0.5, 2.1.0
>
>
> The Audit mechanism is based on LOG4J, configured to use the {{JDBCAppender}} 
> to store the audit statements into the {{SyncopeAudit}} table in the internal 
> storage.
> Besides this base mechanism, we can introduce the {{AuditAppender}} 
> interface, whose instances can:
> # declare which event(s) they will be invoked with
> # declare another LOG4J appender to send the statements to (besides the 
> {{JDBCAppender}} as above)
> # optionally offer the ability to transform the standard statement to a 
> format more suitable to the target appender



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1144) Customizable Audit appender

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085628#comment-16085628
 ] 

ASF subversion and git services commented on SYNCOPE-1144:
--

Commit 21ea877bd398689c81e74a7b760ea1095d13e084 in syncope's branch 
refs/heads/master from [~andrea.patricelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=21ea877 ]

[SYNCOPE-1144] configurable audit appenders with message rewrite option. This 
closes #52.


> Customizable Audit appender
> ---
>
> Key: SYNCOPE-1144
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1144
> Project: Syncope
>  Issue Type: New Feature
>  Components: common, console, core
>Reporter: Francesco Chicchiriccò
>Assignee: Andrea Patricelli
> Fix For: 2.0.5, 2.1.0
>
>
> The Audit mechanism is based on LOG4J, configured to use the {{JDBCAppender}} 
> to store the audit statements into the {{SyncopeAudit}} table in the internal 
> storage.
> Besides this base mechanism, we can introduce the {{AuditAppender}} 
> interface, whose instances can:
> # declare which event(s) they will be invoked with
> # declare another LOG4J appender to send the statements to (besides the 
> {{JDBCAppender}} as above)
> # optionally offer the ability to transform the standard statement to a 
> format more suitable to the target appender



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1144) Customizable Audit appender

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085629#comment-16085629
 ] 

ASF GitHub Bot commented on SYNCOPE-1144:
-

Github user asfgit closed the pull request at:

https://github.com/apache/syncope/pull/52


> Customizable Audit appender
> ---
>
> Key: SYNCOPE-1144
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1144
> Project: Syncope
>  Issue Type: New Feature
>  Components: common, console, core
>Reporter: Francesco Chicchiriccò
>Assignee: Andrea Patricelli
> Fix For: 2.0.5, 2.1.0
>
>
> The Audit mechanism is based on LOG4J, configured to use the {{JDBCAppender}} 
> to store the audit statements into the {{SyncopeAudit}} table in the internal 
> storage.
> Besides this base mechanism, we can introduce the {{AuditAppender}} 
> interface, whose instances can:
> # declare which event(s) they will be invoked with
> # declare another LOG4J appender to send the statements to (besides the 
> {{JDBCAppender}} as above)
> # optionally offer the ability to transform the standard statement to a 
> format more suitable to the target appender



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] syncope pull request #52: [SYNCOPE-1144] configurable audit appenders with m...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/syncope/pull/52


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (SYNCOPE-1161) Option to clone a resource

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-1161:

Fix Version/s: 2.1.0
   2.0.5

> Option to clone a resource
> --
>
> Key: SYNCOPE-1161
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1161
> Project: Syncope
>  Issue Type: Wish
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
>
> Sometimes we need to create a new resource in a connector based in a previous 
> one (for instance to separate the provision types) an option to clone the 
> resource would be nice 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SYNCOPE-1161) Option to clone a resource

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-1161:

Component/s: console

> Option to clone a resource
> --
>
> Key: SYNCOPE-1161
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1161
> Project: Syncope
>  Issue Type: Wish
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
>
> Sometimes we need to create a new resource in a connector based in a previous 
> one (for instance to separate the provision types) an option to clone the 
> resource would be nice 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (SYNCOPE-1162) Change to Connector's display name not reflected by contextual menu

[JIRA]

Francesco Chicchiriccò created SYNCOPE-1162:
---

 Summary: Change to Connector's display name not reflected by 
contextual menu
 Key: SYNCOPE-1162
 URL: https://issues.apache.org/jira/browse/SYNCOPE-1162
 Project: Syncope
  Issue Type: Bug
  Components: console
Affects Versions: 2.0.4
Reporter: Francesco Chicchiriccò
Priority: Minor
 Fix For: 2.0.5, 2.1.0


In the Topology page, if changing the display name of an existing Connector, 
the contextual menu keeps showing the previous one until the page is reloaded.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SYNCOPE-1160) When editing a resource disable the first Previous button

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-1160:

Fix Version/s: 2.1.0
   2.0.5
  Component/s: console

> When editing a resource disable the first Previous button
> -
>
> Key: SYNCOPE-1160
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1160
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
>
> When editing a resource disable the first Previous button:
> it will go to the "Specify the type of the provisioning object" that should 
> not be editable at that time



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (SYNCOPE-1161) Option to clone a resource

[Filipe Silva (JIRA)]

Filipe Silva created SYNCOPE-1161:
-

 Summary: Option to clone a resource
 Key: SYNCOPE-1161
 URL: https://issues.apache.org/jira/browse/SYNCOPE-1161
 Project: Syncope
  Issue Type: Wish
Affects Versions: 2.0.4
Reporter: Filipe Silva
Priority: Minor


Sometimes we need to create a new resource in a connector based in a previous 
one (for instance to separate the provision types) an option to clone the 
resource would be nice 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (SYNCOPE-1160) When editing a resource disable the first Previous button

[Filipe Silva (JIRA)]

Filipe Silva created SYNCOPE-1160:
-

 Summary: When editing a resource disable the first Previous button
 Key: SYNCOPE-1160
 URL: https://issues.apache.org/jira/browse/SYNCOPE-1160
 Project: Syncope
  Issue Type: Bug
Affects Versions: 2.0.4
Reporter: Filipe Silva
Priority: Minor


When editing a resource disable the first Previous button:
it will go to the "Specify the type of the provisioning object" that should not 
be editable at that time



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (SYNCOPE-1145) Connector and Resource configuration versioning

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò resolved SYNCOPE-1145.
-
Resolution: Fixed

> Connector and Resource configuration versioning
> ---
>
> Key: SYNCOPE-1145
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1145
> Project: Syncope
>  Issue Type: New Feature
>  Components: common, console, core
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.5, 2.1.0
>
>
> It often happens that, while playing with Connectors' and Resources' 
> configuration, everything works up until a certain point, then some 
> misconfiguration happens and errors start appearing.
> In such situations, it would be handy to have a simple mechanism to revert to 
> a previous (working) situation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1145) Connector and Resource configuration versioning

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085491#comment-16085491
 ] 

ASF subversion and git services commented on SYNCOPE-1145:
--

Commit bfd47df70afe3e0ea11d9250f06993ddb7aa7ce8 in syncope's branch 
refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=bfd47df ]

[SYNCOPE-1145] Adjusting L for google-diff-match-patch now used by Admin 
Console


> Connector and Resource configuration versioning
> ---
>
> Key: SYNCOPE-1145
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1145
> Project: Syncope
>  Issue Type: New Feature
>  Components: common, console, core
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.5, 2.1.0
>
>
> It often happens that, while playing with Connectors' and Resources' 
> configuration, everything works up until a certain point, then some 
> misconfiguration happens and errors start appearing.
> In such situations, it would be handy to have a simple mechanism to revert to 
> a previous (working) situation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Access Tokens label in dashboard panel

[Massimiliano Perrone]

Il 13/07/2017 10:08, Francesco Chicchiriccò ha scritto:

On 12/07/2017 19:02, Colm O hEigeartaigh wrote:

(Active) SSO Tokens?


+1 for "SSO Tokens"


+1



Regards.

On Wed, Jul 12, 2017 at 4:51 PM, Francesco Chicchiriccò 
 wrote:



Hi ,
I am not completely sure that "Access Token" is actually misleading -
wikipedia does not even mention OAuth about it:

https://en.wikipedia.org/wiki/Access_token

Anyway, if you think so we can change that label; only, I don't 
think that

anything about "session" should be used, as JWT are not sessions.

Other proposals?

Regards.

On 12/07/2017 17:19, Colm O hEigeartaigh wrote:


Yeah makes sense.

Colm.

On Tue, Jul 11, 2017 at 8:53 PM, Massimiliano Perrone <
massimiliano.perr...@tirasa.net> wrote:

Hi guys,

the dashboard page has four tabs. As you know one of this is called
Access
Tokens...

Maybe we should change that name because access token is the standard
name
of an OAuth token so it's misleading. Maybe we can use something like
sessions or authenticated sessions or authenticated users...

WDYT?

Best regards,

Massi




--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)

[jira] [Commented] (SYNCOPE-1151) Glinch in the root realm information

[Matteo Alessandroni (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085422#comment-16085422
 ] 

Matteo Alessandroni commented on SYNCOPE-1151:
--

Hi,

Root realm can't be propagated to external resources, so the solution should be 
not to show the 'Assigned resources' block when in '/' realm.
I'll open a PR for that.

Matteo

>  Glinch in the root realm information
> -
>
> Key: SYNCOPE-1151
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1151
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_032.png, Selection_033.png
>
>
> A small incoherence in the root real info screen and edit screen:
> Choosing the realms (left side) or choosing the root ( / ) realm gives (see 
> Selection_032.png file)
> !Selection_032.png|thumbnail!
> but after creating an realm "below" the root it gives (see Selection_033.png 
> file)
> !Selection_033.png|thumbnail!
> (I highlight the change)
> I think that the last one is the correct one because that in the only way to 
> in the edit realm screen of the root ( / ) to be able to edit the assigned 
> resources (because it also changes) 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1145) Connector and Resource configuration versioning

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085399#comment-16085399
 ] 

ASF GitHub Bot commented on SYNCOPE-1145:
-

Github user mat-ale commented on the issue:

https://github.com/apache/syncope/pull/50
  
Good to hear that!
You're welcome.
Matteo


> Connector and Resource configuration versioning
> ---
>
> Key: SYNCOPE-1145
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1145
> Project: Syncope
>  Issue Type: New Feature
>  Components: common, console, core
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.5, 2.1.0
>
>
> It often happens that, while playing with Connectors' and Resources' 
> configuration, everything works up until a certain point, then some 
> misconfiguration happens and errors start appearing.
> In such situations, it would be handy to have a simple mechanism to revert to 
> a previous (working) situation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] syncope issue #50: Connector and Resource configuration versioning in Admin ...

[mat-ale]

Github user mat-ale commented on the issue:

https://github.com/apache/syncope/pull/50
  
Good to hear that!
You're welcome.
Matteo


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (SYNCOPE-1145) Connector and Resource configuration versioning

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085397#comment-16085397
 ] 

ASF GitHub Bot commented on SYNCOPE-1145:
-

Github user ilgrosso commented on the issue:

https://github.com/apache/syncope/pull/50
  
Merged, thanks @mat-ale!


> Connector and Resource configuration versioning
> ---
>
> Key: SYNCOPE-1145
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1145
> Project: Syncope
>  Issue Type: New Feature
>  Components: common, console, core
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.5, 2.1.0
>
>
> It often happens that, while playing with Connectors' and Resources' 
> configuration, everything works up until a certain point, then some 
> misconfiguration happens and errors start appearing.
> In such situations, it would be handy to have a simple mechanism to revert to 
> a previous (working) situation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] syncope issue #50: Connector and Resource configuration versioning in Admin ...

[ilgrosso]

Github user ilgrosso commented on the issue:

https://github.com/apache/syncope/pull/50
  
Merged, thanks @mat-ale!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] syncope pull request #50: Connector and Resource configuration versioning in...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/syncope/pull/50


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (SYNCOPE-1154) Edit resource to show always in the same order in list of object provision rules

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085338#comment-16085338
 ] 

ASF GitHub Bot commented on SYNCOPE-1154:
-

Github user asfgit closed the pull request at:

https://github.com/apache/syncope/pull/53


> Edit resource to show always in the same order in list of object provision 
> rules
> 
>
> Key: SYNCOPE-1154
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1154
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_034.png
>
>
> In the Edit resource the order of provision rules list by object types 
> changes after editing.
> It should have a fixed order (maybe by object type name?) and not be time 
> dependent or arbitrary



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (SYNCOPE-1154) Edit resource to show always in the same order in list of object provision rules

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò resolved SYNCOPE-1154.
-
Resolution: Fixed

> Edit resource to show always in the same order in list of object provision 
> rules
> 
>
> Key: SYNCOPE-1154
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1154
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_034.png
>
>
> In the Edit resource the order of provision rules list by object types 
> changes after editing.
> It should have a fixed order (maybe by object type name?) and not be time 
> dependent or arbitrary



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1154) Edit resource to show always in the same order in list of object provision rules

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085337#comment-16085337
 ] 

ASF subversion and git services commented on SYNCOPE-1154:
--

Commit 13f9e9b9b34659ef36ce3631b7e26073e72125e1 in syncope's branch 
refs/heads/master from [~skylark17]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=13f9e9b ]

Keep resource provision list order after editing for SYNCOPE-1154 - This closes 
#53


> Edit resource to show always in the same order in list of object provision 
> rules
> 
>
> Key: SYNCOPE-1154
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1154
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_034.png
>
>
> In the Edit resource the order of provision rules list by object types 
> changes after editing.
> It should have a fixed order (maybe by object type name?) and not be time 
> dependent or arbitrary



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1154) Edit resource to show always in the same order in list of object provision rules

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085336#comment-16085336
 ] 

ASF subversion and git services commented on SYNCOPE-1154:
--

Commit b683a76836c1fa19170bfbf85c6330c644f7c506 in syncope's branch 
refs/heads/2_0_X from [~skylark17]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=b683a76 ]

Keep resource provision list order after editing for SYNCOPE-1154


> Edit resource to show always in the same order in list of object provision 
> rules
> 
>
> Key: SYNCOPE-1154
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1154
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_034.png
>
>
> In the Edit resource the order of provision rules list by object types 
> changes after editing.
> It should have a fixed order (maybe by object type name?) and not be time 
> dependent or arbitrary



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] syncope pull request #53: Keep resource provision list order after editing f...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/syncope/pull/53


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] syncope issue #53: Keep resource provision list order after editing for SYNC...

[mat-ale]

Github user mat-ale commented on the issue:

https://github.com/apache/syncope/pull/53
  
Great! 
Thanks.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Access Tokens label in dashboard panel

[Francesco Chicchiriccò]

On 12/07/2017 19:02, Colm O hEigeartaigh wrote:

(Active) SSO Tokens?


+1 for "SSO Tokens"

Regards.


On Wed, Jul 12, 2017 at 4:51 PM, Francesco Chicchiriccò  
wrote:


Hi ,
I am not completely sure that "Access Token" is actually misleading -
wikipedia does not even mention OAuth about it:

https://en.wikipedia.org/wiki/Access_token

Anyway, if you think so we can change that label; only, I don't think that
anything about "session" should be used, as JWT are not sessions.

Other proposals?

Regards.

On 12/07/2017 17:19, Colm O hEigeartaigh wrote:


Yeah makes sense.

Colm.

On Tue, Jul 11, 2017 at 8:53 PM, Massimiliano Perrone <
massimiliano.perr...@tirasa.net> wrote:

Hi guys,

the dashboard page has four tabs. As you know one of this is called
Access
Tokens...

Maybe we should change that name because access token is the standard
name
of an OAuth token so it's misleading. Maybe we can use something like
sessions or authenticated sessions or authenticated users...

WDYT?

Best regards,

Massi


--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/

[jira] [Commented] (SYNCOPE-1154) Edit resource to show always in the same order in list of object provision rules

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085331#comment-16085331
 ] 

ASF GitHub Bot commented on SYNCOPE-1154:
-

Github user ilgrosso commented on the issue:

https://github.com/apache/syncope/pull/53
  
Thanks @mat-ale LGTM, please squash your commits and I'll gladly merge.


> Edit resource to show always in the same order in list of object provision 
> rules
> 
>
> Key: SYNCOPE-1154
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1154
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_034.png
>
>
> In the Edit resource the order of provision rules list by object types 
> changes after editing.
> It should have a fixed order (maybe by object type name?) and not be time 
> dependent or arbitrary



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (SYNCOPE-1154) Edit resource to show always in the same order in list of object provision rules

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò reassigned SYNCOPE-1154:
---

Assignee: Francesco Chicchiriccò

> Edit resource to show always in the same order in list of object provision 
> rules
> 
>
> Key: SYNCOPE-1154
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1154
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_034.png
>
>
> In the Edit resource the order of provision rules list by object types 
> changes after editing.
> It should have a fixed order (maybe by object type name?) and not be time 
> dependent or arbitrary



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] syncope issue #53: Keep resource provision list order after editing for SYNC...

[ilgrosso]

Github user ilgrosso commented on the issue:

https://github.com/apache/syncope/pull/53
  
Thanks @mat-ale LGTM, please squash your commits and I'll gladly merge.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (SYNCOPE-1154) Edit resource to show always in the same order in list of object provision rules

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085320#comment-16085320
 ] 

ASF GitHub Bot commented on SYNCOPE-1154:
-

GitHub user mat-ale opened a pull request:

https://github.com/apache/syncope/pull/53

Keep resource provision list order after editing for SYNCOPE-1154

Hi,

this fixes 
[[SYNCOPE-1154]](https://issues.apache.org/jira/browse/SYNCOPE-1154)

Regards,
Matteo

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mat-ale/syncope SYNCOPE-1154

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/syncope/pull/53.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #53


commit 2d4a52c1311134099eeac7d4a1d5cd033b3e1b3b
Author: Matteo Alessandroni 
Date:   2017-07-12T07:20:42Z

Keep resource provision list order after editing for SYNCOPE-1154




> Edit resource to show always in the same order in list of object provision 
> rules
> 
>
> Key: SYNCOPE-1154
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1154
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Affects Versions: 2.0.4
>Reporter: Filipe Silva
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
> Attachments: Selection_034.png
>
>
> In the Edit resource the order of provision rules list by object types 
> changes after editing.
> It should have a fixed order (maybe by object type name?) and not be time 
> dependent or arbitrary



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] syncope pull request #53: Keep resource provision list order after editing f...

[mat-ale]

GitHub user mat-ale opened a pull request:

https://github.com/apache/syncope/pull/53

Keep resource provision list order after editing for SYNCOPE-1154

Hi,

this fixes 
[[SYNCOPE-1154]](https://issues.apache.org/jira/browse/SYNCOPE-1154)

Regards,
Matteo

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mat-ale/syncope SYNCOPE-1154

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/syncope/pull/53.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #53


commit 2d4a52c1311134099eeac7d4a1d5cd033b3e1b3b
Author: Matteo Alessandroni 
Date:   2017-07-12T07:20:42Z

Keep resource provision list order after editing for SYNCOPE-1154




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---