[SYNCOPE-533] Attribute visibility

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.1.8
• Component/s: common, console, core
• Assignee: Unassigned
• Reporter: Quirino A. Gervacio Jr.
• Created: 08/Jul/14 09:45
• Updated: 08/Jul/14 09:47
• Resolved: 08/Jul/14 09:47

Description

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).

Issue Links

• duplicates: SYNCOPE-131 Assign membership and role schemas to either all memberships / roles or only some memberships / roles