[JIRA] Resolved: (SSPCPP-339) Extraction of contacts and other built-in metadata information

[Scott Cantor (JIRA)]

     [ https://issues.shibboleth.net/jira/browse/SSPCPP-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Cantor resolved SSPCPP-339.
---------------------------------

    Resolution: Fixed

http://svn.shibboleth.net/view/cpp-sp?rev=3562&view=rev

Plugin supports language-aware extraction of errorURL, organization elements, and contacts.

> Extraction of contacts and other built-in metadata information
> --------------------------------------------------------------
>
>                 Key: SSPCPP-339
>                 URL: https://issues.shibboleth.net/jira/browse/SSPCPP-339
>             Project: Shibboleth SP - C++
>          Issue Type: New Feature
>          Components: Attribute Resolution / Filtering, Error Handling
>    Affects Versions: 2.4
>            Reporter: Olivier Salaün
>            Assignee: Scott Cantor
>            Priority: Minor
>             Fix For: 2.5
>
>   Original Estimate: 3 days
>          Time Spent: 2 days, 6 hours, 30 minutes
>  Remaining Estimate: 1 hour, 30 minutes
>
> The usual issue with user attributes occurs when the IdP was not properly configured to release user attributes required by the SP-protected application. That's one of the most common issue and it's hard to make the user do the right thing to fix it. The best that can be done by the SP-protected application developper is to provide an appropriate error message like "You could not access this service because your institution authentication service did not provide us the required user profile. Please contact the authentication service administrator at your institution.". However it might be a long way from the end user to the IdP admin.
> We first thought we would facilitate this through a web page/form on our federation web site. Whenever such issues happen, the SP-protected applications would be responsible for sending the end user to this page. The goal of this page, given an IdP entityID, to look for the contacts for the IdP in the metadata. If the user hits the "submit" button an appropriate error message could be sent to the IdP admins.
> I then thought that the form could be implemented in the Shibboleth SP because the SP is already capable of parsing metadata + it knows its own entityID + it knows the IdP entityID.
> So the feature request would be to add a contextual error page that would be assist the end-user to send a notification to the IdP admins.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira