[JIRA] Resolved: (SC-176) aacli utility doesn't set peer entity role metadata for requester

Scott Cantor (JIRA) noreply at shibboleth.net
Tue Apr 10 03:28:16 BST 2012


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

Scott Cantor resolved SC-176.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 1.3.6
         Assignee: Scott Cantor  (was: Chad La Joie)

Fixed in rev. 1022

> aacli utility doesn't set peer entity role metadata for requester
> -----------------------------------------------------------------
>
>                 Key: SC-176
>                 URL: https://issues.shibboleth.net/jira/browse/SC-176
>             Project: Shibboleth Common - Java
>          Issue Type: Improvement
>          Components: Attribute Authority
>            Reporter: Scott Cantor
>            Assignee: Scott Cantor
>            Priority: Minor
>             Fix For: 1.3.6
>
>
> The aacli "environment" sets up peer entity information for the request, but it doesn't set the requester's role metadata, only the entity descriptor. So it supports group lookup in a filter policy, but not requested attributes in metadata, because the role is null.
> It should go ahead and fetch the matching SAML 1 or SAML 2 SPSSODescriptor role and set that in the request context.

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


More information about the commits mailing list