OpenConext / OpenConext/OpenConext-oidcng
Support for Remote Token Introspection
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4
- Forks
- 6
- Avg merge
- 5d 32m
- Merged PRs (30d)
- 3
Description
To support advances usecases in the context of SRAM and European Universities (Eurotech), we need to support so-called Remote Token Introspection. Basically this is a new spec that specifies how an AS/OIDC proxy can introspect tokens that have been issued by a different AS or proxy (both of which need to be part of the same trust framework).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue proposes remote token introspection for an AS or OIDC proxy that trusts another authorization server or proxy. Start by reviewing the project's existing authentication and token-introspection entry points; done would require an agreed design and support for the described cross-provider trust flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100