View Source

Team members

TBD

The new generation of the eduGAIN Attribute Release Check will be based on the SUNET Attribute Release Check. It will be shown as an eduGAIN Service.

Requirements:

eduGAIN branding (Naming, Logo, header, footer, etc).
All the changes will be contributed upstream to the SUNET Attribute Release Check.
eduGAIN instance need a history of tests, which comprehends the full IdP information as well as the registration authority.
DB backend provided by MySQL (MariaDB).
the eduGAIN instance will be based on docker containers.
Support for the entity categories/attributes and specifications already available in the legacy eduGAIN Attribute Release Check.
Provide a short summary of the results (one/two lines per test).

Due date: TBD

Evaluate adoption of a PHP web framework.

Kanban board:

Repositories:

Slack channel:

Every other Friday at 11:00 CET/CEST

Next meetings:

Date	Participants	Notes
24 Oct 2025	Andrijana Todosijevic Björn Mattsson Davide Vaghetti Valentin Pocotilenco	AMRES implementation Successfully implemented the release check in AMRES, UI is still SWAMID. Interface theming and templating Structure is ok (header/footer/logo/links) In the index page many texts refer to SWAMID, a possible solution for that could be a simple html template. In order to better understand what we want to achieve and how it should look we need mockups for every page. https://github.com/SUNET/swamid-release-check-sp/blob/main/www/html/config.template.php#L20 should have same syntax as https://github.com/SUNET/swamid-metadata-sp/blob/main/web/html/config.template.php#L63 to make it easy for those running both. eduGAIN checks We need to define the list of checks than need to be run on the eduGAIN instance.