Plugin Error for Confluence Module - component-import

[J M]

There's a non-fatal error with a Seraph SSO module I've written for Confluence. The module still works because SSO plugins aren't lik eother plugins, but Confluence marks it as disabled which is creating log noise and is confusing in the Admin section. I cannot figure out how to make this error go away. Any thoughts? The module I'm writing is HttpHeaderSSOAuthenticator.

2014-02-11 11:11:43,294 ERROR [main] [atlassian.plugin.parsers.XmlDescriptorParser] createModuleDescriptor There were problems loading the module 'component-import' in plugin 'HttpHeaderSSOAuthenticator'. The module has been disabled.
2014-02-11 11:11:43,295 ERROR [main] [atlassian.plugin.parsers.XmlDescriptorParser] createModuleDescriptor Cannot find ModuleDescriptor class for plugin of type 'component-import'.
com.atlassian.plugin.PluginParseException: Cannot find ModuleDescriptor class for plugin of type 'component-import'.

[Joe Clark · Accepted solution]

Hi JM,

Seraph modules are not plugins - you should not build them as a plugin or attempt to use plugin framework features (like atlassian-plugin.xml or plugin modules) from within the Seraph extension points.

Seraph modules can be written as simple, vanilla jars that are just dropped into Confluence's WEB-INF/lib directory (and then referenced through configuration of the seraph-config.xml file)

This definitely makes writing custom SSO Authenticators more painful, since the plugin framework has lots of nice extensibility features. Unfortunately it's a bit of a chicken-and-egg problem, since the plugin framework is not initialized until after the Seraph framework is up and running - it's not possible for a Seraph authenticator to use the plugin framework features because Seraph is required to function even if the plugin framework is still starting up.

If you're looking for some guidance on how to structure your authenticator in this case, here's an example I wrote: https://bitbucket.org/jaysee00/example-confluence-sso-authenticator/src

Hope this helps!

[J M]

Okay, that makes sense and I was making too many assuptions about how the plugin loader worked. I originally wasn't building the SSO module as part of the SDK/plugin framework for Confluence. However when I adapted it for JIRA, I ended up using the SDK because I couldn't get the code to compile any other way (missing dependences no matter how I set it up). I did the same for the Confluence JAR to keep things consistent and just assumed I was missing something about how the SDK should be configured. I'll just build with the SDK and then rip everything out of the Jar but my classes.

[Joe Clark]

Sounds good! Feel free to ask further questions here if you get stuck.

[Kevin O_Neal]

Not related to Seraph SSO.

You might be using the wrong plugin-version. You should be on plugin-version 2.

In your atlassian-plugin.xml file:

<atlassian-plugin key="" name="" plugins-version="2">