[EXT] Re: Windows IDP Upgrade from 4.3.3 to 5.1.3 fails
Mittel, Don
dmittel at depaul.edu
Thu Aug 8 19:47:13 UTC 2024
Well the installation completed and I installed Jetty, but I'm getting the following error with my ldap lookup. Nothing of this has change with the previous version
ERROR [org.springframework.webflow.execution.FlowExecutionException:144] -
org.springframework.webflow.execution.FlowExecutionException: Exception thrown in state 'CallAuthenticationFlow' of flow 'authn'
at org.springframework.webflow.engine.impl.FlowExecutionImpl.wrap(FlowExecutionImpl.java:573)
Caused by: org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [org.ldaptive.auth.PooledBindAuthenticationHandler] for bean with name 'authHandler' defined in file [D:\Shibboleth\IdP\conf\authn\ldap-authn-config.xml]
at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1556)
Caused by: java.lang.ClassNotFoundException: org.ldaptive.auth.PooledBindAuthenticationHandler
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:445)
I don't recall seeing anything about this as part of the upgrade documentation. So, again I'm probably missing something simple.
Thanks,
Don
-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Mittel, Don via users
Sent: Thursday, August 8, 2024 12:56 PM
To: Cantor, Scott <cantor.2 at osu.edu>; Shib Users <users at shibboleth.net>
Cc: Mittel, Don <dmittel at depaul.edu>
Subject: RE: [EXT] Re: Windows IDP Upgrade from 4.3.3 to 5.1.3 fails
Thanks Scott. I figured it out, I had forgotten to update my Java_Home system variable to point to the new Java version. Once I did that the installation completed without an issue.
Don
-----Original Message-----
From: Cantor, Scott <cantor.2 at osu.edu>
Sent: Thursday, August 8, 2024 12:39 PM
To: Shib Users <users at shibboleth.net>
Cc: Mittel, Don <dmittel at depaul.edu>
Subject: [EXT] Re: Windows IDP Upgrade from 4.3.3 to 5.1.3 fails
[You don't often get email from cantor.2 at osu.edu. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
Of course, don't confuse the fact that the old IdP may actually be runinng under 17 with what the installer ends up using. I don't use Windows but I imagine it's doing some registry hack to decide what Java to run when something wants to luanch it.
The MSI no longer does anything re: the IdP itself but run the standard installer we use for all platforms.
It's sole reason to exist now is a) allergy to command lines and b) the firewall/ACL changes it historically automates.
-- Scott
--
For Consortium Member technical support, see https://shibboleth.atlassian.net/wiki/x/ZYEpPw
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users
mailing list