[JIRA] Resolved: (SSPCPP-245) Support for attribute requirements in the SP

[Scott Cantor (JIRA)]

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

Scott Cantor resolved SSPCPP-245.
---------------------------------

    Resolution: Fixed

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

Hook mechanism for post-session processing implemented along with a handler to enforce presence of attributes via simple list or full XML AccessControl syntax (overkill).

Machinery added to example config file:
- sessionHook and metadataAttributePrefix to App defaults
- Metadata attribute extractor for support info
- AttributeChecker handler checking for eppn

> Support for attribute requirements in the SP
> --------------------------------------------
>
>                 Key: SSPCPP-245
>                 URL: https://issues.shibboleth.net/jira/browse/SSPCPP-245
>             Project: Shibboleth SP - C++
>          Issue Type: New Feature
>          Components: Configuration, Error Handling, Request Processing
>            Reporter: Leif Johansson
>            Assignee: Scott Cantor
>            Priority: Minor
>             Fix For: 2.5
>
>   Original Estimate: 2 weeks
>          Time Spent: 5 hours
>  Remaining Estimate: 1 week, 4 days, 3 hours
>
> Evaluating attribute requirements for applications is something most applications have to do and it would be great to be able to delegate it to the SP. 
> Here is how I think about how this would work: The SP (either in shibboleth2.xml and/or in web server configuration directives) lists required and optional attributes (future versions could support more complex models based on xacml). Before passing the request up to the application the SP would check that the required attributes are available. If they are not available then the SP displays a message (based on a template) showing the missing attributes. The SP admin can then modify this template to include information about how the user/idp admin should go about fixing the problem.
> Finally the SP should include attribute requirements in Metadata and this is the only reason for including the optional attributes which should probably not be checked by the SP.

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