[JIRA] Updated: (SSPCPP-323) Export info to application about how attributes, etc are being provided.

[Scott Cantor (JIRA)]

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

Scott Cantor updated SSPCPP-323:
--------------------------------

    Affects Version/s:     (was: 2.4)
        Fix Version/s:     (was: 2.5)

If you want to take a stab at coming up with requirements on this, that's fine, otherwise I'm going to pull this from 2.5 for lack of definition.

> Export info to application about how attributes, etc are being provided.
> ------------------------------------------------------------------------
>
>                 Key: SSPCPP-323
>                 URL: https://issues.shibboleth.net/jira/browse/SSPCPP-323
>             Project: Shibboleth SP - C++
>          Issue Type: New Feature
>          Components: Other
>         Environment: n/a
>            Reporter: Steven Carmody
>            Assignee: Scott Cantor
>            Priority: Minor
>
> The Drupal/Shib plugin and the new WordPress/Shib plugin allow the "application administrator" to map Shibboleth provided attributes and values to Roles within the application. Currently, the application admin has to configure into the plugin the Header (or ENV) names, which are then populated into a popup on an admin screen.  Increasingly, these "application administrators" are going to be different people form the person responsible for the Shib install. 
> It would be nice if the Shib SP could provide the app with info about 1) which method Shib will be using to provide the attributes, and 2) the names of the variables the Shib instance will use to provide these values. This would allow these application plugins to more fully automate the process of integrating with Shib.
> Obviously, there's a "bootstrap" problem -- how would SHib tell the app which method is being used. There's also some overlap with the forthcoming federated apps recommendations.

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