Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
titleTechnical details

Initial technical details:

The project is supposed to represent a web portal, where users (i.e. dusters) will access using their federated credentials. The users will, upon invitation, be able to assert Sirtfi tag for the entity under their control. The flow will resemble https://access-check.edugain.org/. The more detailed description can be found here: https://docs.google.com/document/d/1Hwdi7iO3v2U-RrzgT_EhL7AA0xkE9RIr_bQac2IhZ3M

Initial technical implementation:

Initial implementation contains Access Check tool in conjunction with Jagger tool. Access Check tool is used to identify the owner of the entity (which is intended to be tagged), and to create an account on Jagger (for said owner/administrator). Jagger is a federation management tool, and is therefore capable of editing federation metadata. Once an account is created for the administrator of the entity in question, the administrator can then use Jagger to add a desired entity category. More technical details, including the user flow, can be found here. Installation instructions can be found under 'Activity Results'.

Architecture rationale:

The tool needs to achieve two goals:

  • Identify the owner of the service in question
  • Provides the ability to 'tag', i.e. add an entity category for the metadata of  the service

The straightforward way to identify the owner of the service is to look at its eduGAIN metadata, and identify the "owner" email of the service, for which we used a technical support email from the metadata. Access Check tool is capable of consuming metadata, identifying the necessary email, and creating an account (i.e. username/password) for the owner of the service. This is then "exported" to Jagger, where an account is created with credentials obtained from the Access Check tool. Jagger is then capable of adding entity categories and generating metadata, in essence creating an xml file that contains the desired entity category for the service.

...

Panel
titleSustainability
The assumption is that the solution will be a software product that can be operated by a collaborative organization or a technical partner on their behalf.
The software product resulting of this activity will be made available under appropriate open source license so development may continue even after the work finished in the GEANT project


Panel
titleGAP analysis

The first version of the tool is done. The consideration for potential future activities can be found here.


Activity Results

Panel
titleResults

First version of the tool contains Jagger and Access Check tool. See github: tbd

The tools is a combination of 2 services with a Service and an Identity Provider

Requirements for both parts: mariaDB, Apache2, shib2 module for apache

Part 1: Community Tagging Access installation instructions

Part 2: Enities Managment Tool


There are also three demo videos available considering different perspectives and functionalitiesThree demo videos considering the admin and user perspective: Video 1, Video 2, Video 3


Meetings

...