Support privacy properties

[dlabrecq]

Need to support privacy properties as shown in the following user profile mockup.
https://redhat.invisionapp.com/share/3ZBFATW28#/screens

The properties appear to be booleans for:

1. Display name in your public profile
2. Display email in your public profile
3. Display activity in your public profile
4. Display Spaces in your public profile
5. Display work items assigned in your public profile

We could temporarily store some extra properties in the user contextInformation object. However, I'm thinking we may want to make this part of the user's profile, along with properties like email, bio, etc.?

[alexeykazakov]

Yes, we need to support fine-grained privacy. The whole profile can be returned by backend only when accessed via request with user's access token. Otherwise we should check privacy properties and include only public info in our User/Identity payloads.

[sbose78]

Wondering if we should have more than 2 levels ( "only me" and "public").
I feel there should be at least 3 levels.

1. Visible only to me.
2. Visible only to space collaborators.
3. Visible to public.

[hectorj2f]

Afaik, there would be four: super user, admin, collaborator and read-only user. It isn't clear to me which are the boundaries of each user, in terms of privileges.

[alexeykazakov]

Moved to fabric8-services/fabric8-auth#35
Closing.