Affiliation scope origin and configuration: unexpectedly removed value

[Thomas Blanchard]

Thank you Peter,

It turns out a different config for the prod IdP's customer config is present in one of the federation we integrate with the same EntityID and a different shibmd:Scope policy.

So I'll look into having them use a different EntityID, use the federation MD or load my customer's MD before the Federation.

Thomas


--

Thomas Blanchard

________________________________
From: users <users-bounces at shibboleth.net> on behalf of Peter Schober <peter.schober at univie.ac.at>
Sent: Tuesday, June 26, 2018 11:04
To: users at shibboleth.net
Subject: Re: Affiliation scope origin and configuration: unexpectedly removed value

* Thomas Blanchard <tblanchard at linkedin.com> [2018-06-26 16:38]:
> I'm wondering if this is linked to the shibmd:Scope extension regex,
> but I did some testing with different values (updating IdP MD with
> static values, and allow all regex) without solving this problem.

Did you try md:Scope elements without regexes for comparison?

You're only dealing with 2 scopes here from your examples,
"example.edu.ex" and "other-example.net". Try listing them both
as multiple Scope elements.

-peter
--
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20180626/202bb2a4/attachment.html>