OpenConext / OpenConext/OpenConext-deploy

eduID / eduBadges / mobile API integration

Open
#551 0 comments 0 reactions 1 assignee View on GitHub

@baszoetekouw is already working on this.

Since Sep 15, 2025.

Dominant language
Jinja
Stars
16
Forks
20
Avg merge
4d 23h
Merged PRs (30d)
2

Description

In eduID there is an endpoint to fetch all linked schac_home and eppn values for a certain user. EduID is acting as Resource Sever for this endpoint and the endpoint is secured with an access_token scoped on the user. EduBadges already uses this endpoint for some time.

The new mobile app for edubadges will use new mobile API endpoints in eduBadges server. One the calls is /mobile/api/login where the user is retrieved based on an access_token obtained by the mobile app in the OIDC flow of SURFconext. Part of the user info are the eppn values. In theory those can change or disappear , so the eduBadges server will call the links endpoint in eduID again, using the access_token of the mobile app. The scope that is used therefore already existed in Manage, but was not exposed in the well_known_configuration. This has been added in https://github.com/OpenConext/OpenConext-deploy/commit/7fc6032e7b39981737afd972f568d28e05cd15c0.

Request is a new release of OIDC-NG and oidc-playground-server on the test (NOT test2) to test the new flow. Locally it already works.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.