Changes between Version 7 and Version 8 of ServiceProviderFederation/IdpBlacklist


Ignore:
Timestamp:
02/06/23 15:49:38 (16 months ago)
Author:
André Moreira
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ServiceProviderFederation/IdpBlacklist

    v7 v8  
    1 [=#topofpage]
    2 
    3 ''Responsible for this page: [wiki:People/andmor André Moreira].'' \\
    4 ''Last content check: 08-06-2017''
     1''Responsible for this page: [wiki:People/andmor André Moreira].'' \\ ''Last content check: 08-06-2017''
    52
    63{{{
    … …  
    85<h3>Purpose</h3>
    96}}}
    10 
    117This page describes how to request changes to the IdP blacklist of the CLARIN SPF AAI, while providing an overview of the current status of the blacklist and ongoing blacklist requests.
    128
    13 
    149== People ==
    15 
    16 [wiki:People/andmor André Moreira] - SPF AAI operator and blacklist maintainer \\
    17 [wiki:People/dietuyt Dieter Van Uytvanck] - SPF AAI general manager \\
     10[wiki:People/andmor André Moreira] - SPF AAI operator and blacklist maintainer \\ [wiki:People/dietuyt Dieter Van Uytvanck] - SPF AAI general manager \\
    1811
    1912----
    2013== General workflow ==
    21 
    2214Changes 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.
    2315
    24 1. Someone finds a suspicious IdP.
    25 2. Someone (with a CLARIN "developer" account) creates a TRAC ticket targeting the ''AAI IdP Blacklist'' component, to request the removal of this IdP. (The central office will take on this ticket.)
    26 3. TTF-AAI will review the requirements and comments whether any violations have been found.
    27 4. The central office closes the ticket and if there is a violation, CLARIN's pyFF configuration is updated to blacklist the IdP in question.
    28 
     16 1. Someone finds a suspicious IdP.
     17 1. Someone (with a CLARIN "developer" account) creates a TRAC ticket targeting the ''AAI IdP Blacklist'' component, to request the removal of this IdP. (The central office will take on this ticket.)
     18 1. TTF-AAI will review the requirements and comments whether any violations have been found.
     19 1. The central office closes the ticket and if there is a violation, CLARIN's pyFF configuration is updated to blacklist the IdP in question.
    2920
    3021----
    3122== Creating a blacklist request ==
    32 
    3323Changes to the CLARIN IdP blacklist must be requested via TRAC according to the following guidelines:
    3424
    35 0. Make sure there isn't a previous ticket regarding the same issue in the ''AAI IdP Blacklist'' [#Tickets ticket list].
    36 1. [https://trac.clarin.eu/newticket Create a new ticket] in trac.clarin.eu with the following header details:
    37   * Type: '''task'''.
    38   * Component: '''AAI IdP Blacklist'''.
    39   * Owner: '''< default >'''.
    40   * Fill in the summary field including the target IdP name and briefly describing the issue.
    41   * Select the ticket's desired priority.
    42   * (optional) Insert any relevant email address in the CC field.
    43   * (optional) Add some appropriate keywords e.g. ''idp blacklist aai spf''.
     25 0. Make sure there isn't a previous ticket regarding the same issue in the ''AAI IdP Blacklist'' [#Tickets ticket list].
     26 0. [https://trac.clarin.eu/newticket Create a new ticket] in trac.clarin.eu with the following header details:
     27   * Type: '''task'''.
     28   * Component: '''AAI IdP Blacklist'''.
     29   * Owner: '''< default >'''.
     30   * Fill in the summary field including the target IdP name and briefly describing the issue.
     31   * Select the ticket's desired priority.
     32   * (optional) Insert any relevant email address in the CC field.
     33   * (optional) Add some appropriate keywords e.g. ''idp blacklist aai spf''.
    4434
    45 2. On the ticket ''description'' make sure to include:
    46   * The '''entityID''' of the IdP in question.
    47   * The motivation for the request
    48   * Date and time of any previous login attempt via the IdP in question (if known).
     35 2. On the ticket ''description'' make sure to include:
     36   * The '''entityID''' of the IdP in question.
     37   * The motivation for the request
     38   * Date and time of any previous login attempt via the IdP in question (if known).
    4939
    5040As an example, you can use as guidance any [ticket:1008 previously issued ticket] of the ''AAI IdP Blacklist'' component.
    … …  
    5242----
    5343== Open tickets (ongoing blacklist requests) ==
    54 
    5544[[TicketQuery(status=accepted|assigned|new|reopened,component=AAI IdP Blacklist,order=priority,format=table,col=summary|priority|owner|reporter)]]
    56 
    5745
    5846----
    5947== Status ==
    60 
    6148=== Current blacklist ===
    62 
    6349||= entityID =||= Federation =||= Date Blacklisted =||= Reason =||= Notes =||
     50|| https://login-idp.libraries.ch/idp/shibboleth || SWITCHaai || 06/02/2023 || Allows creation of accounts to anyone. [https://www.libraries.ch/faq?locale=en ref] || ||
    6451|| https://idp.protectnetwork.org/protectnetwork-idp || eduGAIN || <unknown> || <unknown> || - ||
    6552|| https://idp.painless-security.com/idp/shibboleth || eduGAIN || <unknown> || <unknown> || - ||
    … …  
    6956|| https://idp.umons.ac.be/idp/shibbolethe || Belnet || <unknown> || <unknown> || - ||
    7057|| https://openidp.aco.net/saml || ACOnet || <unknown> || <unknown> || - ||
    71