Azure AD Connector from IDP v4.1 - canonicalization failure
Ullfig, Roberto Alfredo
rullfig at uic.edu
Wed Aug 31 14:59:06 UTC 2022
Thanks, the property file wasn't being loaded. So I assume the registry and resolver can live side by side just fine. Should we start converting from resolver to registry?
Roberto Ullfig - rullfig at uic.edu
Enterprise Applications & Services | Technology Solutions
University of Illinois - Chicago
From: Cantor, Scott <cantor.2 at osu.edu>
Sent: Wednesday, August 31, 2022 9:40 AM
To: Wessel, Keith W (UIUC) <kwessel at illinois.edu>; Ullfig, Roberto Alfredo <rullfig at uic.edu>; Shib Users <users at shibboleth.net>
Subject: Re: Azure AD Connector from IDP v4.1 - canonicalization failure
On 8/31/22, 10:38 AM, "Wessel, Keith" <kwessel at illinois.edu> wrote:
> Also worth checking in services.xml to see if you have the attribute
> registry enabled. This is related to what Scott suggested.
It's always "enabled", just a question of whether it's loading any rules outside the resolver or not, yes. Older services.xml files won't contain the registry resource bean and default to loading only the resolver file.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users