URNs as Entity IDs

Uniform Resource Names as Entity IDs

The use of Uniform Resource Names (URNs) as entity IDs in the InCommon Federation is NOT RECOMMENDED. If an URN is used, the URN namespace MUST be owned by (or delegated to) the organization, that is, the organization MUST document the existence of a valid authorization chain rooted in a namespace listed in the Official IANA Registry of URN Namespaces.

To illustrate, suppose Internet2 submitted SP metadata with entity ID:

urn:mace:incommon:internet2.edu:sp

This particular entity ID would be acceptable since:

1. The urn:mace namespace is registered with IANA.
2. InCommon is authorized by MACE to use the urn:mace:incommon namespace.
3. Internet2 is authorized by InCommon to use the urn:mace:incommon:internet2.edu namespace (by virtue of the fact that the latter appears in metadata signed by InCommon Operations).

Therefore the entity ID shown above is valid since there exists a valid authorization chain rooted in an official registered namespace (urn:mace).

Historical Note

Historically, InCommon assigned an URN to all new IdPs, based on the IdP's primary DNS domain name:

<EntityDescriptor entityID="urn:mace:incommon:example.edu">

However, InCommon no longer issues URNs to IdPs and instead strongly encourages the use of URLs instead. Type the following command to produce a list of legacy URNs in InCommon metadata:

# list the URNs in metadata
$ curl --silent http://md.incommon.org/InCommon/InCommon-metadata.xml \
  | grep -F '"urn:mace:incommon' \
  | sed -e 's/^.*"\(urn:mace:incommon[^"]*\).*$/\1/' \
  | wc -l
      76

Simply omit the last command in the pipe (wc) to produce the actual list.