Skip to content

Proposal: run the EMA Resource AS scenarios against Keycloak as a real-implementation reference #595

Open

Description

@richardli515

Context

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.

Keycloak 26.7 ships an experimental ID-JAG receiver (--features=identity-assertion-jwt), i.e. it can act as the Resource AS that accepts an ID-JAG via the jwt-bearer grant:
https://www.keycloak.org/26.7/securing-apps/identity-assertion-jwt-authorization-grant

Proposal

Start small, as an example rather than a requirement:

  1. 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.
  2. Instructions for running resource-authorization-server --suite … against it, and the results we get today.
  3. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions