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

Francesco Chicchiriccò updated SYNCOPE-676:
-------------------------------------------
    Description: 
Current {{UserService#list}} / {{UserService#search}} and {{RoleService#list}} 
/ {{RoleService#search}} will barely return all details available for each user 
/ role: attributes (plain, derived, virtual), resources, memberships (user 
only).

In production environments, though, this might cause unnecessary information 
transfer and delays (especially for virtual attributes which might trigger 
remote connections).

It is useful to provide some kind of mechanism (ideally an optional parameter, 
defaulting to {{true}}) to skip additional details return, for usage with admin 
console.

  was:
Current {{UserService#list}} / {{UserService#search}} and {{RoleService#list}} 
/ {{RoleService#search}} will barely return all details available for each user 
/ role: attributes (plain, derived, virtual), resources, memberships (user 
only).

In production environments, though, this might cause unnecessary information 
transfer and delays (especially for virtual attributes which might trigger 
remote connections).

It is useful to provide some kind of mechanism (ideally an optional parameter, 
defaulting to {{true}}) to skip additional details logging, for usage with 
admin console.


> Option for getting simplified list of users and roles
> -----------------------------------------------------
>
>                 Key: SYNCOPE-676
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-676
>             Project: Syncope
>          Issue Type: Improvement
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>             Fix For: 1.2.5, 2.0.0
>
>
> Current {{UserService#list}} / {{UserService#search}} and 
> {{RoleService#list}} / {{RoleService#search}} will barely return all details 
> available for each user / role: attributes (plain, derived, virtual), 
> resources, memberships (user only).
> In production environments, though, this might cause unnecessary information 
> transfer and delays (especially for virtual attributes which might trigger 
> remote connections).
> It is useful to provide some kind of mechanism (ideally an optional 
> parameter, defaulting to {{true}}) to skip additional details return, for 
> usage with admin console.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to