You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Proposal: run the EMA Resource AS scenarios against Keycloak as a real-implementation reference #595
The EMA Resource AS scenarios (#470, #490, #594) are currently only exercised against the in-repo MockResourceAuthorizationServer. That shows the checks work, but not how they behave against a real implementation.
Start small, as an example rather than a requirement:
An optional, documented setup (e.g. examples/keycloak/ with a docker-compose + realm import) that configures Keycloak as a Resource AS trusting the runner-hosted IdP — identity provider, confidential client, federated user link.
Instructions for running resource-authorization-server --suite … against it, and the results we get today.
If maintainers find it useful: an optional / manually triggered CI job.
Goal is a setup that's easy to run, so it can serve as a reference for future auth scenarios. Not proposing to change how existing tests run.
Open questions
Is an external-implementation example in scope for this repo, or better kept outside it?
Keycloak's feature is based on draft-01 of the ID-JAG spec, while the scenarios reference draft-04, so some checks may differ. Is that useful signal or noise?
Happy to put together a first version if there's interest.
Activity