[
https://issues.apache.org/jira/browse/SYNCOPE-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò closed SYNCOPE-533.
------------------------------------------
Resolution: Duplicate
> Attribute visibility
> --------------------
>
> Key: SYNCOPE-533
> URL: https://issues.apache.org/jira/browse/SYNCOPE-533
> Project: Syncope
> Issue Type: New Feature
> Components: common, console, core
> Affects Versions: 1.1.8
> Reporter: Quirino A. Gervacio Jr.
>
> Ability to limit the visibility of User attributes (normal, derived, virtual)
> to specific to roles (also child roles) from UI to REST
> Implementation would be is/are additional input(s) when creating User
> attributes.
> Example:
> Visibility: <roleid rolename>
> Is visible to sub role? true|false
> Use case:
> Project Application1 (Syncope) will be used by other applications (currently
> we have 2 applications Application2 and Application3) to manage its users,
> and role hierarchy. Application2 has only 5 to 10 attributes as of now
> however Application3 is estimated to have at least 50+ attributes. When a
> user is created, attributes from both applications is mixed.
> We opted to use prefixing such as PTP_AllowTrade or RET_LetFly however for us
> this implementation doesn't seem to cut it.
> Please advice if this is worth it to implement.
> Currently i am implementing the ability to limit the visibility of Reports to
> specific roles (andor child).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
