Versions Compared

Key

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

...

There are appropriate circumstances for automatic suspension when:

  • A Participant incur in commits a severe violation as defined on section 3.5.
  • The violation is unambiguous and not disputable, for example a missing signature of required policy document.

...

  • In the period preceding suspension, the eduGAIN Service  will make every effort to contact the federation representatives to solve the problem.
  • Suspended federations will be listed in a separate section of the members status page on the eduGAIN technical site. The reason for the suspension will be visible in the details window.
  • Suspended federations' metadata upstream feed will not be pulled and no validation alerts will be sent until the status is changed by the OT. The status page will still have the link to metadata validation, so that the federation is able to test its current feed before asking us to lift the suspension.
  • To make sure that the federation is aware of the problem a weekly reminder will be sent automatically.
  • The suspension will be lifted after the federation contacts the eduGAIN Service and informs about rectifying rectifys the problem.
  • The eduGAIN Service will inform the Assembly and the Steering Committee about cases of applying or lifting automatic suspensions and will report on suspended federations on at each SC meeting.

Suspension workflow

One week after the deadline for remediate to the violation, the eduGAIN Support will send the first suspension forewarn to inform the technical contacts and the , delegate and deputy of the Identity Federation that a failure in fixing the issue will lead to suspension.

...