Changes between Version 18 and Version 19 of ServiceProviderFederation/LoginTest


Ignore:
Timestamp:
07/05/16 09:00:24 (8 years ago)
Author:
Sander Maijers
Comment:

contents: add AAggregator

Legend:

Unmodified
Added
Removed
Modified
  • ServiceProviderFederation/LoginTest

    v18 v19  
    1 = Testing user access to applications/resources within the Service Provider Fedaration =
     1= Testing user access to applications/resources within the Service Provider Federation =
    22
    33Please see [https://www.clarin.eu/content/creating-and-testing-shibboleth-sp] for an introduction to this topic.
    44
    5 == How to test an SP (for SP admins in eduGAIN) ==
     5In sum,
     61. each CLARIN SPF SP and IdP need to know each other by consuming SAML metadata about that IdP, respectively SP.
     72. Furthermore, the IdP must release attributes to the SP, to help authorize and identify the user.
     8
     9Whether or not this workflow works for a certain SP-IdP combination must be tested, since isses surface regularly, especially regarding the second step.
     10
     11== How to test an SP ==
     12
     13=== For regular CLARIN SPF SPs: AAggregator ===
     14
     151. Log in with the IdP to be tested for any AAgregator-enabled SP, such as the LINDAT/CLARIN repository SP https://lindat.mff.cuni.cz/repository/xmlui/login .
     162. Please visit https://lindat.mff.cuni.cz/services/aaggreg/ (AAggregator web app), you can log in with any IdP for that.
     17
     18Find the entry with the correct timestamp and IdP-SP combination.
     19The report you see shows the attribute release (quality) for various recently attempted IdP-SP combinations.
     20If too few attributes have been released, this can cause problems with our SPs.
     21‘Bad’ results, where attribute release quality is insufficient for normal CLARIN applications, are called out there.
     22The results should then be studied with the SP operator, and if needed the IdP operator should be notified of the problem with a view to having the IdP release more attributes.
     23
     24=== For SPs that consume SAML metadata about eduGAIN IdPs ===
    625
    726You can use https://access-check.edugain.org for testing authentication with different user profiles through "eduGAIN Access Check" IdP.
     
    928== How to test an SP (for testers) ==
    1029
    11 You will get tickets if people like you to test their SP with a detailed description on where to find the login to test. In case of an error, please provide the error to the SP that created the ticket. You can recall your willingness to test logins at any time. Keep in mind, the longer the list is, the fewer logins every person has to perform. To have testers for every country is an important task, on the way to ensure proper configuration of all SPs.
     30You will get tickets if people like you to test their SP with a detailed description on where to find the login to test. In case of an error, please provide the error to the SP that created the ticket.
     31You can recall your willingness to test logins at any time. Keep in mind, the longer the list is, the fewer logins every person has to perform.
     32To have testers for every country is an important task, on the way to ensure proper configuration of all SPs.
    1233
    13 == List of testers per country (identity federation) ==
    14 '''We are looking for volunteers.'''
     34== List of testers per country (i.e., identity federation) ==
     35
     36'''We are looking for volunteers!'''
    1537
    1638=== Belgium ===
     
    3355
    3456=== Netherlands ===
    35   * [//wiki/sander%2540clarin.eu Sander Maijers], Tilburg University and Max Planck Institute for Psycholinguistics
     57
     58* Dieter van Uytvanck <dieter@clarin.eu>: Universiteit Utrecht
    3659
    3760=== Norway ===