problems seemingly caused by transientID in O365

Aaron Howell aaron.howell at deakin.edu.au
Wed Aug 27 08:33:09 EDT 2014


Or if you want to use less XML, this should be equivalent to what Paul posted.

<afp:PolicyRequirementRule xsi:type="basic:NOT">
    <basic:Rule xsi:type="basic:OR”>
        <basic:Rule xsi:type="basic:AttributeRequesterString" value="http://randomsp1.com/" />
        <basic:Rule xsi:type="basic:AttributeRequesterString" value="http://randomsp1.com/" />
        <basic:Rule xsi:type="basic:AttributeRequesterString" value="http://randomsp1.com/" />
     </basic:Rule>
</afp:PolicyRequirementRule>

Cheers,
Aaron

On 27 Aug 2014, at 10:15 pm, Paul Hethmon <paul.hethmon at clareitysecurity.com> wrote:

> On Aug 27, 2014, at 7:57 AM, Rob Gorrell <rwgorrel at uncg.edu> wrote:
>
>> My question is, why is the transientID being released? Is it a case of first match wins in policy processing order instead of most restrictive? If that is so, I could use a little help on the XML, how can I modify the transientID release to include multiple basic:NOT conditions (to not release to Google AND Microsoft)?
>
> Rob,
>
>
>        <afp:PolicyRequirementRule xsi:type="basic:AND">
>
>            <basic:Rule xsi:type="basic:NOT">
>                <basic:Rule xsi:type="basic:AttributeRequesterString" value="http://randomsp1.com/" />
>            </basic:Rule>
>            <basic:Rule xsi:type="basic:NOT">
>                <basic:Rule xsi:type="basic:AttributeRequesterString" value="http://randomsp2.com" />
>            </basic:Rule>
>            <basic:Rule xsi:type="basic:NOT">
>                <basic:Rule xsi:type="basic:AttributeRequesterString" value="http://randomsp3.com" />
>            </basic:Rule>
>
>        </afp:PolicyRequirementRule>
>
>
> cheers,
>
> Paul
>
> Paul Hethmon
> Chief Software Architect
> paul.hethmon at clareitysecurity.com
>
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net


Important Notice: The contents of this email are intended solely for the named addressee and are confidential; any unauthorised use, reproduction or storage of the contents is expressly prohibited. If you have received this email in error, please delete it and any attachments immediately and advise the sender by return email or telephone.

Deakin University does not warrant that this email and any attachments are error or virus free.


More information about the users mailing list