Attribute Transcoding errors following IdP upgrade

[Simon McLeish]

OK, so why would it not be loading the resolver file (in the extra lookup
instance where it doesn't work) when it did before? And why does it still
work for a "normal" authentication through the IdP?

On Tue, Sep 22, 2020 at 3:25 PM Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 9/22/20, 10:19 AM, "users on behalf of Simon McLeish" <
> users-bounces at shibboleth.net on behalf of simon.mcleish at gmail.com> wrote:
>
> >    Wouldn't those rules be expected to work the same in 3.4.6 and 4.0.1?
>
> If you mean to encode attributes outbound, yes, those will work as is the
> same as they did before, provided it's loading the resolver file into the
> registry service's configuration set.
>
> -- 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20200922/7b443a70/attachment.htm>