| Version 2 (modified by , 7 years ago) (diff) |
|---|
Responsible for this page: André Moreira.
Last content check: 08-06-2017
Purpose
This page describes how to request changes to the !IdP blacklist of the CLARIN SPF AAI, while at the same time aims to provide an overview of the current status of the blacklist and ongoing blacklist requests.
People
André Moreira - SPF AAI operator and blacklist maintainer
Dieter Van Uytvanck - SPF AAI general manager
General workflow
Changes to the IdP blacklist can be requested if an SP operator objects, or has doubts about the inclusion of certain IdP(s) in the CLARIN SPF AAI. Either because this IdP looks suspicious or by any other technical or organizational reason. By default, all available IdPs are included in the CLARIN SPF AAI when the respective national federation joins CLARIN, so in other for an IdP to be removed, a request must be made to the central office by means of a trac ticket. The process is the same when an SP operator intends to to re-add a previously blacklisted IdP.
- Someone finds a suspicious IdP.
- Someone with a CLARIN "developer" role creates a ticket on TRAC with respect to the "AAI IdP Blacklist" component, requesting the removal of this IdP. (The central office will take on this ticket.)
- TTF-AAI will review the requirements and comments whether any violations have been found.
- The central office closes the ticket and if there is a violation, CLARIN's pyFF configuration is updated to blacklist the IdP in question.
Change request
Tickets
| Ticket | Summary | Priority | Owner | Reporter |
|---|---|---|---|---|
| #1008 | Suspicious IdP UNICON | critical | ||
| #1081 | TU-Dresden not releasing attributes | minor |
