Changes between Version 2 and Version 3 of ServiceProviderFederation/IdpBlacklist


Ignore:
Timestamp:
06/08/17 13:11:17 (7 years ago)
Author:
André Moreira
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ServiceProviderFederation/IdpBlacklist

    v2 v3  
    99}}}
    1010
    11 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.
     11This 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.
    1212
    1313
    … …  
    2323
    24241. Someone finds a suspicious IdP.
    25 2. 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.)
     252. 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.)
    26263. TTF-AAI will review the requirements and comments whether any violations have been found.
    27274. The central office closes the ticket and if there is a violation, CLARIN's pyFF configuration is updated to blacklist the IdP in question.
    … …  
    2929
    3030----
    31 == Change request ==
     31== Creating a blacklist request ticket ==
    3232
     33Changes to the CLARIN IdP blacklist must be requested via TRAC according to the following guidelines:
    3334
     350. Make sure there isn't a previous ticket regarding the same issue in the ''AAI IdP Blacklist'' [#Tickets ticket list].
     361. [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''.
     44
     452. 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).
     49
     50As an example, you can use as guidance any [ticket:1008 previously issued ticket] of the ''AAI IdP Blacklist'' component.
    3451
    3552----
    36 == Tickets ==
     53== Open tickets (!IdPs undergoing evaluation) ==
    3754
    3855[[TicketQuery(status=accepted|assigned|new|reopened,component=AAI IdP Blacklist,order=priority,format=table,col=summary|priority|owner|reporter)]]
    … …  
    4057
    4158----
    42 == Status, Planning and Roadmap ==
     59== Status ==
    4360
     61=== Current blacklist ===
    4462
    45 ----
    46 == Resources ==
     63||= entityID =||= Federation =||= Date Blacklisted =||= Reason =||= Notes =||
     64|| https://idp.protectnetwork.org/protectnetwork-idp || eduGAIN || <unknown> || <unknown> || - ||
     65|| https://idp.painless-security.com/idp/shibboleth || eduGAIN || <unknown> || <unknown> || - ||
     66|| https://idp1.proofidcloud.co.uk/idp/shibboleth || eduGAIN || <unknown> || <unknown> || - ||
     67|| https://sso-demo.proofidcloud.co.uk/idp/pingfederate || eduGAIN || <unknown> || <unknown> || - ||
     68|| https://idp.umons.ac.be/idp/shibbolethe || Belnet || <unknown> || <unknown> || - ||
     69|| https://openidp.aco.net/saml || ACOnet || <unknown> || <unknown> || - ||
    4770
    48