Shibb IDP issue

[Cantor, Scott]

> We aren't using Shibb IDP for LDAP-authentication hence we don't have
> anything defined in ldap-auth-config file. I checked on this file and this
> default-file has been retained since 2019 and has remained the same
> during the shibb IDP upgrade process. Can we remove this file all together
> if this has got refences to JNDI?

That isn't how JNDI comes into play, and that file is not used if you're not using the Password login flow so it doesn't matter. The choice of LDAP implementation is not feature-specific or configured in terms of IdP settings, it's property-driven generally.

https://shibboleth.atlassian.net/wiki/spaces/IDP4/pages/1265631798/LDAPonJava

> We are using header based logic for providing shibb IDP sessions and we
> have defined the ldap connections in the ldap.properties file and using the
> LDAP data connector in the attribute-resolver file for pulling the user
> attributes. 

The use of LDAP in any capacity means using specific implementations of the protocol, and the IdP hasn't shipped with settings that would use JNDI in a while. That's all I'm telling you.

I don't know why your stack trace is what it is, but it's too edited down to be exposing what component is actually doing whatever it was doing. Get the full trace and it would perhaps be clearer.

The process log by default logs edited stack traces, the warn log defaults to the full stacks.

Since V4 is superseded and V5 uses a completely different LDAP implementation from earlier versions anyway, the best answer is to not waste a ton of time trying to debug an LDAP problem and upgrade to see if that helps.

-- Scott