Thank you again, Mike for the help, I really appreciate it!  I figured out the 
issue.  I was building with Java 8, however, my Docker image had Tomcat 8 with 
Java 7.  The Docker image now has Java 8, and everything is working as 
expected!  I was able to figure this out by bumping up the log level to debug.  
Once debug was enabled, I saw the major/minor exception in the stack trace.

Thanks again! :-)

Matt

From: Mike Jumper <[email protected]>
Reply-To: "[email protected]" 
<[email protected]>
Date: Tuesday, June 7, 2016 at 2:32 PM
To: "[email protected]" <[email protected]>
Subject: Re: Error Loading Authentication Provider Class (0.9.9-incubator)

On Tue, Jun 7, 2016 at 10:52 AM, Matthew Ramella 
<[email protected]<mailto:[email protected]>> wrote:
Hello,

We’ve recently upgraded to the Apache incubator version of Guacamole.  I have 
rebuilt our authentication provider extension using the latest incubator 
Guacamole common and ext JARS, and I have updated the guacamoleVersion in my 
guac-manifest.json file to 0.9.9-incubating.  Unfortunately, we’re seeing the 
following error: Authentication provider class cannot be loaded (wrong version 
of API?).

I’m wondering if there’s something I’m missing on my side?

Hi Matt,

Are you sure you rebuilt everything? That particular error indicates that the 
JVM failed to load the class because it implements an incompatible version of 
AuthenticationProvider. If the extension got that far in the loading process, 
then the "guacamoleVersion" sanity check passed, so that much is definitely OK, 
but it somehow must still be using a different version of 
AuthenticationProvider if the JVM refused to load the class.

I'd recommend:

1) Doing a full "mvn clean install" of guacamole-client, such that all .jars 
are rebuilt and installed to the local repository
2) Double-checking the pom.xml of your extension, making sure that 
"guacamole-common" and "guacamole-ext" are both "org.apache.guacamole" and 
"0.9.9-incubating".
3) Rebuilding the extension

Assuming all the above has been done, and the new extension has been installed 
in place of the old one, things should work.

Thanks,

- Mike

Reply via email to