Azure & IdP v5.1.3

[Alan Buxey]

Hi,

> DEBUG [net.shibboleth.idp.attribute.filter.AttributeRule:149] - Attribute filtering engine '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/AttributeRule:_a0798fb6385d2de9a09c0a44397262e1' Filtering values for attribute 'azureName' which currently contains 1 values
> DEBUG [net.shibboleth.idp.attribute.filter.matcher.saml.impl.AbstractMatchesShibMDScopeMatcher:93] - Attribute Filter '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/PermitValueRule:_29d4f0f50773b5d6d70e7dd298b68a96': Applying shibmd scope comparison to all values of Attribute 'azureName'
> DEBUG [net.shibboleth.idp.attribute.filter.matcher.saml.impl.AbstractMatchesShibMDScopeMatcher:119] - Attribute Filter '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/PermitValueRule:_29d4f0f50773b5d6d70e7dd298b68a96': returning 0 values
> DEBUG [net.shibboleth.idp.attribute.filter.AttributeRule:158] - Attribute filtering engine '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/AttributeRule:_a0798fb6385d2de9a09c0a44397262e1' Filter has permitted the release of 0 values for attribute 'azureName'


in poxy task 2 (part of step 2) you added a chunk of config....which included:

<AttributeRule attributeID="azureName">
        <PermitValueRule xsi:type="ScopeMatchesShibMDScope" />
    </AttributeRule>

now, if the value being returned doesnt not match the expected scope,
then it will get filtered out.  in Trust task: 3 you were asked to add
the following to the IdP metadata that you'd previously collected

<Extensions>
  <shibmd:Scope regexp="false">your_scope_domain_here</shibmd:Scope>
</Extensions>

your_scope_domain_here   <- this must be set to the valid value
released by the IdP ! (if not, well, the azureName released by the IdP
will have a scope that doesnt match what is expected from the
directions given in the metadata (scapeMathesShibMDScope) and any
values of azureName that dont match the scope expected get filtered
out. - returning 0 values

alan