| | 1 | Date: 29. March 2015 |
| | 2 | Time: 9.00 - 9.45 CEST |
| | 3 | Location: <https://connect.sunet.se/enabling-users> |
| | 4 | |
| | 5 | == Agenda == |
| | 6 | 1. Status updates on work packages |
| | 7 | 2. CLARIN-specific entity category |
| | 8 | |
| | 9 | |
| | 10 | == Attendees == |
| | 11 | * Lukas Hämmerle, GÉANT |
| | 12 | * Wolfgang Pempe, GÉANT |
| | 13 | * Martin Matthiesen, CLARIN |
| | 14 | * Sami Silen, GÉANT |
| | 15 | * Timo Mustonen, GÉANT |
| | 16 | |
| | 17 | |
| | 18 | == Status updates on work packages == |
| | 19 | |
| | 20 | === 1. CLARIN eduGAIN Integration === |
| | 21 | 1.A. Get a long-term agreement for SPF metadata inclusion in eduGAIN |
| | 22 | Wolfgang reported that agreement was signed by DFN directors, next step |
| | 23 | is to send it to CLARIN office in Utrecht. |
| | 24 | |
| | 25 | === 2.A. Attribute Release Check === |
| | 26 | Current test version available http://earc.eduid.hu/ |
| | 27 | Quite some feedback received at GÉANT symposium even without |
| | 28 | specifically announcing the beta version, most comments were received |
| | 29 | regarding the rating mechanism. Needs some refinement, to be discussed |
| | 30 | at separate VC on 5th April, 10.30 (https://connect.sunet.se/enabling-users) |
| | 31 | |
| | 32 | === 2.B. CoCo/R&S support for CLARIN's most wanted-IdPs list. === |
| | 33 | A follow up in a few weeks to see if another reminder (sent |
| | 34 | to the federation operators of affected IdPs/federations) could |
| | 35 | further help improving the impact of the information campaign. |
| | 36 | |
| | 37 | === 2.C. Improving error messages for SPs === |
| | 38 | Instructions: |
| | 39 | https://confluence.csc.fi/display/HAKA/Shibboleth+SP+attribute+checker |
| | 40 | An example SP that is set up like this can be tested here: |
| | 41 | https://devsp.funet.fi/secure/ |
| | 42 | (Use username/password: teppo/testaaja) |
| | 43 | Wiki page currently being moved to eduGAIN wiki |
| | 44 | https://wiki.edugain.org/How_to_configure_Shibboleth_SP_attribute_checker |
| | 45 | |
| | 46 | Sami received some additional feedback on the instructions from Wolfang |
| | 47 | (Debian) and Lukas (Mac OS X). In both cases they worked as expected. |
| | 48 | Sami started to migrate instructions from HAKA confluence wiki to |
| | 49 | eduGAIN wiki, which is a bit cumbersome due to the different wiki syntax |
| | 50 | and other issues. |
| | 51 | |
| | 52 | One feedback was that having the return/target URL shown/added to the |
| | 53 | notification email to the IdP admin is less useful than having the entityID. |
| | 54 | As was learned, the SP entityID can howver not be set/used in a variable |
| | 55 | by SP itself. Lukas added a feature request for Shib SP to have this |
| | 56 | added in next version but it will take a while (months) to have this |
| | 57 | version released and be deployed by SPs. Therefore, it would make sense |
| | 58 | in the short term to set the entityID manually in the templates. |
| | 59 | |
| | 60 | Martin was confused by the attribute name prefix "SHIB_", which is |
| | 61 | not used in the Shibboleth default configuration. The instructions |
| | 62 | should use the values/names used in the the Shibboleth default |
| | 63 | configuration, which would mean removing the "SHIB_" prefix. |
| | 64 | Martin prefers script over web-form based solution to generate |
| | 65 | instructions/configuration files because generating config for multiple |
| | 66 | SPs is easier with script and script typically has to be run only once. |
| | 67 | Martin would be interested in Python script (is available on many server |
| | 68 | OS). |
| | 69 | |
| | 70 | Martin mentioned that this approach to better handle the |
| | 71 | missign-attribute error messages will be discussed CLARIN-internally |
| | 72 | soon. Ideally, Sami |
| | 73 | is included in the discussion to answer questions that might |
| | 74 | pop up and to collect feedback. If inputs from CLARIN is also beneficial |
| | 75 | for generic deployers, these inputs should be taken into account and be |
| | 76 | included in instructions later. Collected inputs/suggestions should be |
| | 77 | discussed first. |
| | 78 | Add perl script and template on Github and link it from Wiki. |
| | 79 | |
| | 80 | |
| | 81 | == 2. CLARIN-specific entity category == |
| | 82 | |
| | 83 | After discussing whether introducing a CLARIN-specific category |
| | 84 | makes sense or not, the consensus was in the end "let's try this", |
| | 85 | especially because the effort of introducing the entity category was |
| | 86 | small. Wolfgang therefore set now the new (clarin.eu) entity category |
| | 87 | value for the CLARIN SPs in the CLARIN SPF metadata. The new entity |
| | 88 | category is thus now available within DFN-AAI and eduGAIN: |
| | 89 | http://clarin.eu/category/clarin-member |
| | 90 | |
| | 91 | The entity category is however not set for those few CLARIN SPs being |
| | 92 | added to eduGAIN by other federations (than DFN-AAI). |
| | 93 | Wolfgang mentions that ideally the entity category value (which is a |
| | 94 | URL) should resolve to a web page on the CLARIN web page. The page |
| | 95 | should explain the use and purpose of the CLARIN entity category. |
| | 96 | Creating this page is something to be done by clarin.eu (Done) |
| | 97 | |
| | 98 | Impact/use of the entity category (regarding attribute release) has |
| | 99 | to be analyzed in a few months. |
| | 100 | |
| | 101 | == Next Meeting == |
| | 102 | * Tuesday 26. April 9.00 CET,10.00 Helsinki time |
| | 103 | https://connect.sunet.se/enabling-users |
| | 104 | |
| | 105 | |
| | 106 | == Actions == |
| | 107 | * Martin to include Sami in CLARIN-specific discussion |
| | 108 | regarding the presentation/discussion |
| | 109 | * Sami to answer questions in that discussion and collect points |
| | 110 | (suggestion for improvements/changes) to discuss at next VC whether |
| | 111 | to integrate them in generic instructions |
