[
https://issues.apache.org/jira/browse/SYNCOPE-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15515933#comment-15515933
]
ASF subversion and git services commented on SYNCOPE-948:
---------------------------------------------------------
Commit ba511b38b39bf7819be68324cb4c3c6ae0bdf53f in syncope's branch
refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=ba511b3 ]
[SYNCOPE-950] Removing readonly property from AttrTO (was useless even before
SYNCOPE-948)
> Optionally provide schema information with attribute values
> -----------------------------------------------------------
>
> Key: SYNCOPE-948
> URL: https://issues.apache.org/jira/browse/SYNCOPE-948
> Project: Syncope
> Issue Type: Improvement
> Components: core
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Fix For: 2.0.1, 2.1.0
>
>
> When searching for users, groups or any objects via REST, there is currently
> the option to specify the {{details}} flag:
> * when {{false}} only (user)name, plain and derived attributes are returned
> * when {{true}} also virtual attributes, roles, relationships and
> memberships are included
> Moreover,
> [attributes|https://github.com/apache/syncope/blob/2_0_X/common/lib/src/main/java/org/apache/syncope/common/lib/to/AttrTO.java#L86]
> are returned alongside with the sole "meta" information about the related
> schema being defined as read-only.
> The {{details}} flag above can be used to additionally indicate, when true,
> that the full information about the attributes' schema is to be returned,
> together with value(s).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
