For the basic service we want to have a rather simple attribute model to be exposed by the AAs, only relying on attributes that exist in well known schema. If a VO needs custom attributes, they should be using the advanced services.
COmanage standardizes on eduPerson Schema, but also allows arbitrary attributes to be configured to express roles and rights within the VO. In addition Comanage allows groups and group memberships to be defined.
The following attributes are supported:
| friendly name | OID |
|---|---|
| eduPersonAffiliation | 1.3.6.1.4.1.5923.1.1.1.1 |
| eduPersonEntitlement | 1.3.6.1.4.1.5923.1.1.1.7 |
| eduPersonPrincipalName | 1.3.6.1.4.1.5923.1.1.1.6 |
| eduPersonScopedAffiliation | 1.3.6.1.4.1.5923.1.1.1.9 |
| eduPersonUniqueId | 1.3.6.1.4.1.5923.1.1.1.13 |
| eduPersonOrcid | 1.3.6.1.4.1.5923.1.1.1.16 |
| cn | 2.5.4.3 |
| description | 2.5.4.13 |
| displayName | 2.16.840.1.113730.3.1.241 |
| facsimileTelephoneNumber | 2.5.4.23 |
| givenName | 2.5.4.42 |
| l | 2.5.4.7 |
| labeledURI | 1.3.6.1.4.1.250.1.57 |
| 0.9.2342.19200300.100.1.3 | |
| mobile | 0.9.2342.19200300.100.1.41 |
| o | 2.5.4.10 |
| ou | 2.5.4.11 |
| postalAddress | 2.5.4.16 |
| postalCode | 2.5.4.17 |
| sn | 2.5.4.4 |
| st | 2.5.4.8 |
| street | 2.5.4.9 |
| telephoneNumber | 2.5.4.20 |
| title | 2.5.4.12 |
| uid | 0.9.2342.19200300.100.1.1 |
| isMemberOf | 1.3.6.1.4.1.5923.1.5.1.1 |
Comanage supports eduPerson out of the box so most attributes can be mapped directly form the CoManage data model to