Remove Federation Errors in SAML 2.0 and ADFS 3.0

Rainer Hoerbe rainer at hoerbe.at
Thu Nov 10 15:08:20 EST 2016


Franz,

We have connected such a configuration. The solution was to apply a style sheet to the ADFS metadata before pushing it to the aggregators, removing the non-SAML stuff and adding the missing pieces that our deployment profile requires.

- Rainer


> Am 10.11.2016 um 20:41 schrieb Cantor, Scott <cantor.2 at osu.edu>:
> 
>> 2016-11-10 11:13:37 CRIT Shibboleth.Application: error initializing
>> MetadataProvider: Metadata instance failed manual validation checking.
> 
> Has to be something else in the log, but that means it's literally invalid regardless. ADFS metadata generally loads fine, so this didn't come straight from ADFS or there's a setting used that is mis-configured and it's producing XML that doesn't pass muster.
> 
> There is no workaround for that (other than fixing it, and it would be telling you why in the log).
> 
> -- Scott
> 
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net



More information about the users mailing list