LocalDynamic + MetadataFilters = possible bug?

[Mak, Steve]

Is there documentation I can read that shows a deeper dive into the attribute resolution process?

I need a better understanding of the process order to rule processes out.

Is this the correct order?

md resolution starts > md filters applied > md resolution ends > md resolution cached > ...skip auth/c14n > (sp scoped) attribute resolution > attribute resolution cached > (sp scoped) attribute filtering > build SAML assertion/response

- Steve

On 10/15/20, 08:58, "users on behalf of Cantor, Scott" <users-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:

    On 10/15/20, 8:53 AM, "users on behalf of Mak, Steve" <users-bounces at shibboleth.net on behalf of makst at upenn.edu> wrote:

    >    It's not duplicate metadata either. I've looked through every source found in the metadata providers file and no
    > duplicates.

    Unless it's consistently always unable to attach the tags I don't have any obvious suggestions. I could imagine bugs that would prevent the attachment because of something unexpected or untested in the XML but not something non-repeatable. That sort of problem would almost have to point to an attribute lookup issue.

    -- Scott


    -- 
    For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
    To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net