...
- For COmanage Gears, subjects are namespaced within a CO (by association with CO ID) but are not further partitioned.
- TBD, but for COmanage Gears subjects will be associated with a CO Person ID, which can then be used to translate across other identifiers as needed.
- For COmanage Gears, Opaque IDs are preferred. For domesticated applications, either, but probably NetID more typically.
Grouper responses
- How are subjects namespaced: We use the Internet2 Subject API where each subject has a label of a namespace (source ID). This seems to work fine...
- How is a subject represented? What attributes are built in: Grouper has built in name, description, id, source, and can be searched by identifier or id or either. Also the Subject API has a list of multi-valued attributes, though the WS only transmits them as single valued (and we have never had a request to change this).
- Can you get netId's back from the service or just opaque id's: Grouper allows the caller to specify which attributes are sent back, so the netId can be sent back to the caller on any operation