...
| Tip | ||
|---|---|---|
| ||
| RememberSince an entity ID is a name, not a location, the entity ID and the endpoint locations in metadata do not need to match. An entity ID is a name, not a location. If the entity ID is a URL (and it almost always is) it need not resolve. |
...
However, InCommon no longer issues URNs to IdPs. The use of URNs as entity IDs for new IdPs (or any entity, for that matter) is strongly discouraged and in some situations not allowed.
For new IdPs registered in the Federation, InCommon recommends that URL-based entity IDs be used. For example, an IdP might have the following entity ID:
...
As with IdP naming, you MUST be prepared to commit to maintaining an SP entity ID essentially for the life of the service. Choose a name you can commit to maintaining even if the service will run at a different (or perhaps more than one) location in the futureindependently of the endpoint locations, so if the latter change in the future, the entity ID need not change.
Choosing a Name
Below are some tips and suggestions that might be useful when choosing an entity ID.
...