Closed OIDF-automation closed 2 months ago
I’d address this issue in the detailed list endpoint under discussion in this issue: https://bitbucket.org/openid/connect/issues/2109/federation-advanced-listing-endpoint
The PR that aims to resolve this issue is this https://bitbucket.org/openid/connect/pull-requests/736
This will be addressed by work on the Extended Listing Endpoint specification.
This is being done in he now-adopted specification https://openid.net/specs/openid-federation-extended-listing-1_0.html .
Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/2145
Original Reporter: MichaelFraser99
One use case encountered in the Australian ecosystem has been the ability to filter the list endpoint’s contents on additional values beyond what is currently in the list endpoint. Specifically, the ability to say “give me all entities that were updated after x date” or “give me all entities that were updated between x date and y date”. This enables authorisation servers to identify changes that would result in changes to RP client metadata
This has currently been solved with a proprietary API however we feel the functionality offered through it would be valuable to all consumers of the specification
The proposal is to add two additional query parameters to the list endpoint:
and