Entity Statement Hosting

[Torsten Lodderstedt]

All Entities in a federation SHOULD be prepared to publish an Entity Statement about themselves (Entity Configuration). If they are not able to do so themselves, another issuer MUST do it for them.

I don’t understand why this matters. If it matters, the text should also say that a another party can publish the entity configuration on behalf of the entity. That’s an option we implement in our current federation prototype for the GAIN technical PoC. Our central platform will publish the entity configurations of all our RPs and OPs.

[Torsten Lodderstedt]

I also don’t understand how another issuer can publish the entity configuration of a certain entity as those are by definition self issued.

[Giuseppe De Marco]

I agree, I suggest to remove the text:

“““

If they are not able to do so themselves, another issuer MUST do it for them.

“““

‌

This is misleading considering that an entity configuration is hosted on the fqdn of the entity that issues its entity configuration. So the entity configuration Is self hosted and self issued.

[Giuseppe De Marco]

Fixed by https://bitbucket.org/peppelinux/connect-2/commits/9715f9016741f22721ce1eb9a2dfe60199369503

[Michael Jones]

I agree with this deletion.

[Giuseppe De Marco]

Fixed by https://bitbucket.org/openid/connect/pull-requests/317

[Michael Jones]

Per the discussion on the 6-Oct-22 working group call, we will delete the misleading sentence.

[Giuseppe De Marco]

Closed by https://bitbucket.org/openid/connect/pull-requests/317