Wrong capitalization in IDP4 resolver configuration documentation
Cantor, Scott
cantor.2 at osu.edu
Thu Mar 25 19:34:49 UTC 2021
The schema tagged in git for 4.0.1 also says SASLConfig, not SaslConfig. There's no chance that SaslConfig would pass validation, so it just can't be working that way, let alone only working that way. There's no wildcard that would permit it to validate.
It may have changed pre-4.0.1 while the feature was being added, I vague recall that possibility, but in that case you'd have to be on a snapshot and nothing we released.
-- Scott
On 3/25/21, 3:31 PM, "users on behalf of Cantor, Scott" <users-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:
On 3/25/21, 3:24 PM, "users on behalf of Jim Fox" <users-bounces at shibboleth.net on behalf of fox at washington.edu> wrote:
> I'm looking at https://urldefense.com/v3/__http://shibboleth.net/schema/idp/shibboleth-attribute-resolver.xsd__;!!KGKeukY!iUNj-B-R7jFaRXeilFbN-dnANbZPheY5SfGAxCww_TTPO9uRdzWLCH0g93w4qeU$
That says SASLConfig, the code says it, the warning says it, and the example says it.
> And when I used <SASLConfig> it fails. When I use <SaslConfig> it works.
I can't speak to 4.0.1 but that schema URL is the 4.1 version and it's SASLConfig there. I will check 4.0.1 but at this point what it did or didn't do is not really going to matter other than as a bug that has to be worked around. Our convention would be SASLConfig, certainly, and that's what everything I'm looking at says it is.
I'm more confused by the fact you think that schema or the wiki says SaslConfig...? All I see is SASL.
-- Scott
--
For Consortium Member technical support, see https://urldefense.com/v3/__https://wiki.shibboleth.net/confluence/x/coFAAg__;!!KGKeukY!iUNj-B-R7jFaRXeilFbN-dnANbZPheY5SfGAxCww_TTPO9uRdzWLCH0gTPMHR7o$
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users
mailing list