Team members

TBD

Development 

Roadmap

Milestone 1 - #NAME#

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

Milestone 2- #NAME#

Evaluate adoption of a PHP web framework.

Kanban board: 

https://cryptpad.fr/kanban/#/2/kanban/edit/EF46ZSSsKssdCbXoKjeANINr/

Repositories:

Slack channel:

Meetings

Every other Friday at 11:00 CET/CEST

Link: https://geant.zoom.us/my/davidev?pwd=MGdac2Q4NmhmNkh3Z3RMdytyLzI0dz09

Meeting notes

DateParticipantsNotes

 

Final steps to go into production:

  • 3rd of July:
    • apply the changes made by Valentin Pocotilenco to the old release check and add serveralias to point to release-check-old.edugain.org
    • verify that GRNET has removed all the metadata for the old release check
    • remind PCSS about the DNS change on the 6th of July
  • 6th of July:
    • verify that SWAMID metadata for noec release check are published in eduGAIN.
    • verify that the DNS changes has been applied.
    • send a confirmation email to eduGAIN discuss/assembly and REFEDS maling lists.

 

  • Add a banner on the new release check:
    • "The eduGAIN Attribute Release check has been updated. If you are looking for test results from the previous instance, please check https://release-check-old.edugain.org"
  • Davide and Valentin will meet to turn old release check in read-only mode.
  • Bjorn will communicate DNS names to be registered for the new release check.
  • Need GRNET
  • Production date  

 

  • GEANT ACME Account for edugain.org domain now does require HOST validation (in the past).
  • Keep the old release check online as release-check-old.edugain.org for three months, without test functionalities, but with database access.

 

Next milestone:
  • API Access implementation.
  • Move textresult strings to textresult code.
  • Simplify translations based on textresult


Admin access for federation operators based on eduteams

 

All open issues closed.
We plan to go into production on April on the week starting on the 20th.
Actions:
  • Valentin will commit the implementation of the translation for the php pages by Monday next week.
  • Davide will put the privacy policy for the new release check in the eduGAIN wiki.

 

  • Assurance test:
    • Add both personalized and CoCov2 ECs to assurance test in order to raise the chances to get the assurance attribute.
  • CoCo test:
    • now the test is passed if you release at least three attributes out the requested set

Actions:

  • Valentin to work on adapting the pages for translation.
  • Davide will ask InCommon to have a look to the test EARC.
  • Davide will put the privacy policy in the EARC section of the wiki. 

 

- review of privacy policy (Davide)

- check of test instance from AMRES - feedback by the 20th (Andrijana).

- check of test instance from GARR - feedback by the 20th (Davide)

- ask InCommon to have a look at the current release check to understand how to better (Davide)

  - frame assurance check (currently bound to CoCov2, maybe better to link it to personalized EC) - ( 

- translation (Bjorn/Valentin)

  - make use of gettext to translate strings into the selected language.

  - not going to translate the name of the attributes.

  - implement a language selector and browser based automatic selection.

  - contributed translations will be managed via github on the project repository.

- provide subject-ids or ePPN of the EARC team (everyone)

- Assurance Attribute test: why it requests ePPN? because it is bount to CoCov2 (Bjorn).

- CoCo test: ask for three attributes out of the set of required attributes to be released to pass the test (Bjorn)

- production and metadata for the service providers will be operated and maintained by SUNET once we are ready (Bjorn). 


 

 

AMRES implementation

Successfully implemented the release check in AMRES, UI is still SWAMID.

Interface theming and templating

eduGAIN checks

  • We need to define the list of checks than need to be run on the eduGAIN instance. 


  • No labels