...
Historically, InCommon assigned an URN (Uniform Resource Name) to all new IdPs, based on the IdP's primary DNS domain name:
| Code Block | ||
|---|---|---|
| ||
<EntityDescriptor entityID="urn:mace:incommon:example.edu"> |
...
For new IdPs, InCommon recommends that URL-based entity IDs be used. For example, an IdP might have the following entity ID:
| Code Block | ||
|---|---|---|
| ||
<EntityDescriptor entityID="https://idp_name.example.edu/idp"> |
...
As with IdPs, InCommon recommends that URL-based entity IDs be used in SP metadata. For example, an SP might have the following entity ID:
| Code Block | ||
|---|---|---|
| ||
<EntityDescriptor entityID="https://sp_name.example.edu/sp"> |
...
| Info | ||
|---|---|---|
| ||
The following section is for site administrators registering new entities in InCommon. |
Choosing a New Name
An entity ID must be globally unique to avoid name collisions both within and across federations. To help ensure global uniqueness, an entity ID is almost always an absolute URL but it's important to note that an entity ID is a name, not a location. That is, an entity ID need not resolve to an actual web resource.
...