ldap authenticator problems

Cantor, Scott cantor.2 at osu.edu
Wed Apr 21 20:01:58 UTC 2021


On 4/21/21, 3:09 PM, "users on behalf of Rene Paquin" <users-bounces at shibboleth.net on behalf of rpaquin at wlu.ca> wrote:

>    This is confusing.  I created an IDP instance based on v4.01 with what is in essence the same configuration as
> 4.1 in terms of ldap connector etc and it works but when I switch to v 4.1 I get those ldap authentication errors. 

4.0 and 4.1 are very very different. If you start with 4.0 and upgrade to 4.1, then that's one thing. If you start with 4.1 that's something else. The defaults and settings in those cases are *completely* different. V3 and earlier add yet more combinations.

A bug is possible, but you're talking about a hundred possible settings in many different places that all could vary with a specific set of steps. I can't reproduce something based on generalities.

What I can say is that the bug you logged is *exactly* what happens when there is a definition of a property that is empty or set to a value we don't have defined.

I also can say that I've tested 4.1 from scratch and know that it works when I do things I am familiar with but that's mostly leaving defaults.

I also know that 4.0 settings for LDAP upgraded to 4.1 work and that at least some sets of 3.x settings work all the way through as well.

There's nothing I can do without a bug report with every relevant file, sanitized or not. I can't do anything on list.

-- Scott




More information about the users mailing list