OpenConext / OpenConext/OpenConext-access
connect Resource Server - Relying Party
@gelsenaar is already working on this.
Since Sep 18, 2026.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 0
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 22
Description
In SP dashboard an RS can only be added to an RP if the institution_guid is the same (e.g. both RP and RS are from the same institution).
Question: do we want the RP to be able to request adding an RS that is from another organisation? In production this is not unusual, for example student-mobiliteit.
Answer: for mvp, only resource servers managed by yourself can be added to the relying parties you own.
New Feature Request
Summary
Problem: What is the pain point? (e.g., "Users cannot filter results by date.")
After adding a resource server (RS) (https://github.com/OpenConext/OpenConext-access/issues/835) a user wants to make a connection between the Relying Party (RP) and the RS, or edit the connection between RP's and RS's.
Value: Why should we build this? (e.g., "Improves data accessibility for
power users.")
To create these connections by the user themselves, putting less strain on support.
Proposed Solution
-
Action: Let the user connect RP's to RS's
-
Design: Prototype: https://www.figma.com/proto/81StIVqfOKfwhWVjx7Ew81/SURF-Access?node-id=13446-31135&viewport=142%2C-519%2C0.66&t=eofJhVN8a2ZkNIqC-8&scaling=contain&content-scaling=responsive&page-id=9684%3A52896&hide-ui=1
Designs: https://www.figma.com/design/81StIVqfOKfwhWVjx7Ew81/SURF-Access?node-id=13446-34119&t=0Tx6d9GpdVd5KZ93-1 -
Impact: Does this affect existing APIs or UI components?
Developer Checklist
To be completed by the developer during implementation.
- Add required changes and feature flags config files
- Create and document database changes and migrations
- Create and document API changes and migrations
- check for backwards compatibility
- Updated CHANGELOG and other documentation where needed
Testing and QA
Describe how to verify and test this change.
Test Environment and Setup
- https://test2.surfaccess.nl/
- All users should be able to do this
Test Checklist
- create a OIDC client and Resource server
- browse to the 'afnemers' when creating the resource server
- note that the organization's OIDC clients are available for selection
- select OIDC client and save
- note that in manage resource servers are added to the client
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.
Assessment
This issue has not been assessed yet.