Configuring Attribute Release Consent with SP blacklist

[Lipscomb, Gary]

Hi Etienne,

I'm having trouble getting this to work. Is my code correct?

Regards

Gary

[1] metadata

<md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" ID="_4d35faa8519eba5b810db7474072fbd851cdcfe2" entityID="https://onlinedevel.csu.edu.au/shibboleth">

  <md:Extensions xmlns:alg="urn:oasis:names:tc:SAML:metadata:algsupport">
    <alg:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha512"/>
    <alg:DigestMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#sha384"/>
    <alg:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
    <alg:DigestMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#sha224"/>
    <alg:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
    <alg:SigningMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha512"/>
    <alg:SigningMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha384"/>
    <alg:SigningMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
    <alg:SigningMethod Algorithm="http://www.w3.org/2009/xmldsig11#dsa-sha256"/>
    <alg:SigningMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
    <alg:SigningMethod Algorithm="http://www.w3.org/2000/09/xmldsig#dsa-sha1"/>


    <mdattr:EntityAttributes>
       <saml:Attribute Name="ConsentReleaseRequired">
       <saml:AttributeValue>false</saml:AttributeValue>
       </saml:Attribute>
    </mdattr:EntityAttributes>


  </md:Extensions>

[2] relying-party.xml

       <bean id="shibboleth.NoUserConsentRelyingPartybyTag" parent="RelyingPartyByTag">
             <constructor-arg name="candidates">
                 <list>
                    <bean id="disableCSUMetadata" parent="TagCandidate"
                          c:name="ConsentReleaseRequired"
                          p:values="false" />
                  </list>
             </constructor-arg>
            <property name="profileConfigurations">
                <list>
                    <ref bean="Shibboleth.SSO" />
                    <ref bean="SAML1.AttributeQuery" />
                    <ref bean="SAML1.ArtifactResolution" />
                    <ref bean="SAML2.SSO" />
                    <ref bean="SAML2.ECP" />
                    <ref bean="SAML2.Logout" />
                    <ref bean="SAML2.AttributeQuery" />
                    <ref bean="SAML2.ArtifactResolution" />
                </list>
            </property>
        </bean>

[3] idp-process.log

2016-04-15 13:30:53,298 - DEBUG [net.shibboleth.idp.saml.profile.impl.InitializeRelyingPartyContextFromSAMLPeer:132] - Profile Action InitializeRelyingPartyContextFromSAMLPeer: Attaching RelyingPartyContext based on SAML peer https://onlinedevel.csu.edu.au/shibboleth

2016-04-15 13:30:53,327 - DEBUG [net.shibboleth.idp.relyingparty.impl.DefaultRelyingPartyConfigurationResolver:293] - Resolving relying party configuration

2016-04-15 13:30:53,328 - DEBUG [net.shibboleth.idp.relyingparty.impl.DefaultRelyingPartyConfigurationResolver:305] - Checking if relying party configuration shibboleth.NoUserConsentRelyingPartybyTag is applicable

2016-04-15 13:30:53,329 - DEBUG [net.shibboleth.idp.relyingparty.impl.DefaultRelyingPartyConfigurationResolver:310] - Relying party configuration shibboleth.NoUserConsentRelyingPartybyTag is not applicable

2016-04-15 13:30:53,329 - DEBUG [net.shibboleth.idp.relyingparty.impl.DefaultRelyingPartyConfigurationResolver:314] - No relying party configurations are applicable, returning the default configuration shibboleth.DefaultRelyingParty








> -----Original Message-----
> From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Etienne
> Dysli-Metref
> Sent: Wednesday, 13 April 2016 16:27
> To: users at shibboleth.net
> Subject: Re: Configuring Attribute Release Consent with SP blacklist
>
> On 12/04/16 16:00, Cantor, Scott wrote:
> > It's best to attach an EntityAttribute using a metadata filter, and
> > then base the policy on the tag.
>
> We've added homeOrg and homeOrgType to our federation metadata so
> that IdP operators can easily turn consent off for SPs in their organisation.
>
> <util:list id="shibboleth.RelyingPartyOverrides">
>   <!-- ... more beans -->
>   <bean id="shibboleth.NoUserConsentRelyingParty"
>         parent="RelyingPartyByTag">
>     <constructor-arg name="candidates">
>       <list>
>         <bean id="disableForSingleHomeOrganization"
>               parent="TagCandidate"
>               c:name="urn:oid:2.16.756.1.2.5.1.1.4"
>               p:values="example.org" />
>         <!-- ... more beans -->
>       </list>
>     </constructor-arg>
>     <property name="profileConfigurations">
>       <list>
>         <ref bean="Shibboleth.SSO" />
>         <ref bean="SAML2.SSO" />
>         <!-- ... other profiles -->
>       </list>
>     </property>
>   </bean>
> </util:list>
>
> See [1] pp.22-26 for a bit more details.
>
>   Etienne
>
> [1]
> https://www.switch.ch/aai/support/presentations/shibboleth-training-
> 2015/T3P09-User_Consent.pdf


Charles Sturt University

| ALBURY-WODONGA | BATHURST | CANBERRA | DUBBO | GOULBURN | MELBOURNE | ORANGE | PORT MACQUARIE | SYDNEY | WAGGA WAGGA |

LEGAL NOTICE
This email (and any attachment) is confidential and is intended for the use of the addressee(s) only. If you are not the intended recipient of this email, you must not copy, distribute, take any action in reliance on it or disclose it to anyone. Any confidentiality is not waived or lost by reason of mistaken delivery. Email should be checked for viruses and defects before opening. Charles Sturt University (CSU) does not accept liability for viruses or any consequence which arise as a result of this email transmission. Email communications with CSU may be subject to automated email filtering, which could result in the delay or deletion of a legitimate email before it is read at CSU. The views expressed in this email are not necessarily those of CSU.

Charles Sturt University in Australia
http://www.csu.edu.au
The Grange Chancellery, Panorama Avenue, Bathurst NSW Australia 2795
(ABN: 83 878 708 551; CRICOS Provider Numbers: 00005F (NSW), 01947G (VIC), 02960B (ACT)). TEQSA Provider Number: PV12018


Consider the environment before printing this email.