Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

metadata.federation_entity.jwks equal to federation entity keys? #140

Open
zachmann opened this issue Nov 15, 2024 · 2 comments
Open

metadata.federation_entity.jwks equal to federation entity keys? #140

zachmann opened this issue Nov 15, 2024 · 2 comments
Assignees

Comments

@zachmann
Copy link
Collaborator

The specification defines the "federation entity keys" as the keys used for the trust mechanisms in oid-fed and that those are published in the entity configuration in the jwks claim (as well as in entity statements issued by superiors).

There is also the metadata.federation_entity.jwks claim.
This claim is not defined specifically for the federation_entity entity type, but is a common claim that can be used with all entity types, where section 5.2.1 states "Note that these keys are distinct from the Federation Entity Keys used to sign Entity Statements." which is obviously true for all entity types except federation_entity. It's unclear to me if for federation_entity the jwks there MAY/SHOULD/MUST/MUST NOT be equivalent to the federation entity keys from the entity configuration.

My assumption would be that if metadata.federation_entity.jwks is not omited in an entity statement / configuration is MUST be equal to the jwks claim. However, the note in 5.2.1 suggests the opposite. I think a note clearing this up would make sense.

@peppelinux
Copy link
Member

peppelinux commented Nov 15, 2024

Implementations might include jwks in federation_metadata for specific purposes even if this would not make any sense, as in a jwt header parameter I can configure the iat claim and it will be simply ignored.

The current draft specifies that federation entity keys must be at the top level of the JWT payload, while metadata-specific keys belong within each specific metadata section.

The draft implicitly allows jwks in federation_entity to provide flexibility for future or unknown claims without predefining their usage. Despite the presence of jwks in federation metadata, the draft does not define a concrete approach for their use within the specification's scope. All cryptographic operations related to trust evaluation rely solely on the federation entity keys, jwks in federation entity metadata are therefore ignored.

@selfissued
Copy link
Member

We should indicate in the draft that Federation Entity Keys occur at the top level of the Entity Statement and not in the Federation Entity metadata, to prevent any confusion.

@selfissued selfissued self-assigned this Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants