Date: 29. March 2015 Time: 9.00 - 9.45 CEST Location: <https://connect.sunet.se/enabling-users>
Agenda
- Status updates on work packages
- CLARIN-specific entity category
Attendees
- Lukas Hämmerle, GÉANT
- Wolfgang Pempe, GÉANT
- Martin Matthiesen, CLARIN
- Sami Silen, GÉANT
- Timo Mustonen, GÉANT
Status updates on work packages
1. CLARIN eduGAIN Integration
1.A. Get a long-term agreement for SPF metadata inclusion in eduGAIN Wolfgang reported that agreement was signed by DFN directors, next step is to send it to CLARIN office in Utrecht.
2.A. Attribute Release Check
Current test version available http://earc.eduid.hu/ Quite some feedback received at GÉANT symposium even without specifically announcing the beta version, most comments were received regarding the rating mechanism. Needs some refinement, to be discussed at separate VC on 5th April, 10.30 (https://connect.sunet.se/enabling-users)
2.B. CoCo?/R&S support for CLARIN's most wanted-IdPs? list.
A follow up in a few weeks to see if another reminder (sent to the federation operators of affected IdPs?/federations) could further help improving the impact of the information campaign.
2.C. Improving error messages for SPs
Instructions: https://confluence.csc.fi/display/HAKA/Shibboleth+SP+attribute+checker An example SP that is set up like this can be tested here: https://devsp.funet.fi/secure/ (Use username/password: teppo/testaaja) Wiki page currently being moved to eduGAIN wiki https://wiki.edugain.org/How_to_configure_Shibboleth_SP_attribute_checker
Sami received some additional feedback on the instructions from Wolfang (Debian) and Lukas (Mac OS X). In both cases they worked as expected. Sami started to migrate instructions from HAKA confluence wiki to eduGAIN wiki, which is a bit cumbersome due to the different wiki syntax and other issues.
One feedback was that having the return/target URL shown/added to the notification email to the IdP admin is less useful than having the entityID. As was learned, the SP entityID can howver not be set/used in a variable by SP itself. Lukas added a feature request for Shib SP to have this added in next version but it will take a while (months) to have this version released and be deployed by SPs. Therefore, it would make sense in the short term to set the entityID manually in the templates.
Martin was confused by the attribute name prefix "SHIB_", which is not used in the Shibboleth default configuration. The instructions should use the values/names used in the the Shibboleth default configuration, which would mean removing the "SHIB_" prefix. Martin prefers script over web-form based solution to generate instructions/configuration files because generating config for multiple SPs is easier with script and script typically has to be run only once. Martin would be interested in Python script (is available on many server OS).
Martin mentioned that this approach to better handle the missign-attribute error messages will be discussed CLARIN-internally soon. Ideally, Sami is included in the discussion to answer questions that might pop up and to collect feedback. If inputs from CLARIN is also beneficial for generic deployers, these inputs should be taken into account and be included in instructions later. Collected inputs/suggestions should be discussed first. Add perl script and template on Github and link it from Wiki.
2. CLARIN-specific entity category
After discussing whether introducing a CLARIN-specific category makes sense or not, the consensus was in the end "let's try this", especially because the effort of introducing the entity category was small. Wolfgang therefore set now the new (clarin.eu) entity category value for the CLARIN SPs in the CLARIN SPF metadata. The new entity category is thus now available within DFN-AAI and eduGAIN: http://clarin.eu/category/clarin-member
The entity category is however not set for those few CLARIN SPs being added to eduGAIN by other federations (than DFN-AAI). Wolfgang mentions that ideally the entity category value (which is a URL) should resolve to a web page on the CLARIN web page. The page should explain the use and purpose of the CLARIN entity category. Creating this page is something to be done by clarin.eu (Done)
Impact/use of the entity category (regarding attribute release) has to be analyzed in a few months.
Next Meeting
- Tuesday 26. April 9.00 CET,10.00 Helsinki time
Actions
- Martin to include Sami in CLARIN-specific discussion regarding the presentation/discussion
- Sami to answer questions in that discussion and collect points (suggestion for improvements/changes) to discuss at next VC whether to integrate them in generic instructions
