[JIRA] Commented: (SSPCPP-465) CLONE - Tag entityID not usable in error templates

[martin.haase@idp.protectnetwork.org (JIRA)]

    [ https://issues.shibboleth.net/jira/browse/SSPCPP-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14162#comment-14162 ] 

martin.haase at idp.protectnetwork.org commented on SSPCPP-465:
------------------------------------------------------------

In 2.5 as of 2012-06-14 in the OpenSUSE repo for CentOS6, both ways do not work:
a) the "old" style:
    <RequestMapper type="Native">
      <RequestMap applicationId="default" accessError="accessError.html">
	<AccessControl>
            <RuleRegex require="eppn">.+</RuleRegex>
            [...]
...with an <shibmlp entityID/> in accessError.html that will be empty
b) the new style:
<RelyingParty Name="https://example.org/idp/shibboleth" keyName="myself" sessionHook="/Shibboleth.sso/AttrChecker"/>
and
<Handler type="AttributeChecker" Location="/AttrChecker" template="attrChecker.html"   attributes="eppn" flushSession="true"/>
...with an <shibmlp entityID/> in attrChecker.html that will be empty

in b) also <shibmlp requestURL /> is unusable, however, <shibmlp target /> is.


> CLONE - Tag entityID not usable in error templates
> --------------------------------------------------
>
>                 Key: SSPCPP-465
>                 URL: https://issues.shibboleth.net/jira/browse/SSPCPP-465
>             Project: Shibboleth SP - C++
>          Issue Type: Bug
>    Affects Versions: 2.3.1
>            Reporter: martin.haase at idp.protectnetwork.org
>            Assignee: Scott Cantor
>            Priority: Trivial
>             Fix For: 2.5
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Wanted to customize an error template that outputs the entityID of an IdP as described in:
> https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPErrors
> While <shibmlp supportContact/> works as expected, <shibmlp entityID/> as well as <shibmlp entityId/> remained empty.

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