-
Notifications
You must be signed in to change notification settings - Fork 14
Description
This has been discussed before with no resolution. I just implemented this and found that I needed to encode some solution.
Section 5.2.2. states:
It is RECOMMENDED that, when present, these metadata parameters occur in an Entity's federation_entity metadata.
They MAY also be present in the Entity's metadata for other Entity Types, particularly when the values for those Entity Types
differ from those for the federation_entity metadata.
This means that metadata for any type may find vital information about that entity, not in the metadata of the selected metadata entity type, but in the federation_entity metadata.
This is a problem when a resolve request contains a type parameter.
In the definition of resolve response in section 8.3.2, the content of the metadata parameter is defined as:
metadata
REQUIRED. JSON object containing the resolved subject metadata, according to the requested type and expressed in the
metadata format defined in [Section 3](https://openid.net/specs/openid-federation-1_0.html#entity-statement).
If the requester is to be guaranteed to receive all metadata for the selected type, the federation_entity metadata, if present, must also be returned.
2 possible solutions to this issue is:
- Change the recommendation in 5.2.2 and state that the common attributs must be placed with each entity type they apply to, or
- Enforce that federation_entity metadata is always returned in resolve responses, even if type is provided in the request.
I originally requested the first option (I still like that best), but I have implemented the second to be compliant with the standard and other implementations of it.