| Warning |
|---|
|
A user's attributes typically come primarily from a single source, which is usually an LDAP directory. Local portal users, by contrast, normally have a similar set of attributes which come from the uPortalAccountUserSource (LocalAccountPersonAttributeDao). It would be a useful feature if it were possible for users to have attributes from both of these sources, as well as other similar sources. But what happens when multiple sources define the same attribute? In point of fact, the PersonDirectory API can manage this case in a deterministic and admin-configurable manner, but the resulting behavior isn't well communicated to the user in the UI. How do we establish which attributes may be managed for which data sources using which tools, and how do we communicate that to users in the portal? |
...
| System JIRA | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
...
...
...
...
...
Summary
This proposal describes a service that describes which attributes are mutable for which groups and provides an API for making those changes.
...