Reloadable attribute resolver - Added encoders not showing up
makst at upenn.edu
Wed Jul 15 13:42:27 UTC 2020
Thank you, I thought I was losing my mind. Yes I'm on 4.0.1
I will look into it.
So just for clarity, even though I have not converted over to the new registry system, I still need to reload the registry in order to get new AttributeEncoders to show up?
On 7/15/20, 09:39, "users on behalf of Cantor, Scott" <users-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:
On 7/15/20, 9:35 AM, "users on behalf of Mak, Steve" <users-bounces at shibboleth.net on behalf of makst at upenn.edu> wrote:
> Hi all I had a question to make sure I'm not doing something wrong.
I assume you're using 4.0, I keep tripping over the same thing from muscle memory. The encoders are reloaded as part of the Registry service now, not the Resolver. You would have to make that reloadable. The shipping default is to reload but the property default is not, so upgrades don't have an uncommented property that makes it reloadable. Just diff dist/.../services.properties
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
More information about the users