problems seemingly caused by transientID in O365

[Paul Hethmon]

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