On 22 May 2014, at 14:48, Stefan Paetow <[log in to unmask]> wrote:
> So there was no plan to provide COI names/IDs within the ecosystem? That might mean that we leave it up to the COIs to manage/provide, i.e. part of the rules of a COI might be the requirement to provide a common COI name (of some sort) in RADIUS/SAML where necessary.
COIs would have three things - an internal database ID; a CoI dns-style ID (e.g. pilot.community.moonshot.ja.net); and a friendly name for the community “Moonshot Pilot Community”.
The internal database id would never be seen beyond the database and portal; the CoI ID would be used across the TR-ecosystem; and the friendly name would be displayed in the portal.
Rhys.
--
Dr Rhys Smith
Identity, Access, and Middleware Specialist
Cardiff University & Janet, the UK's research and education network
email: [log in to unmask] / [log in to unmask]
GPG: 0x4638C985
|