[ome-users] Password provider problem

[Josh Moore]

Hi Mark,

it's not exactly related to the classpath, but similar. The indexer and pixeldata processes don't pick up all XML bean configuration files but rather use their own set:

  http://git.openmicroscopy.org/?p=ome.git;a=blob;f=components/server/resources/beanRefContext.xml;h=ac74ced6309db8d67735c42f14ecf819aa9b6f29;hb=master#l83

As a workaround, you can match "ome/services/db-*.xml" rather than "ome/services/service-*.xml". We'll look into either making this clear on the ExtendingOmero page, or by adding an appropriate extension point which will include password providers.

Sorry for hassle!

Cheers,
~Josh.

On Aug 5, 2011, at 3:28 PM, Mark Woodbridge wrote:

> Hi,
> 
> I've written a password provider to authenticate using our active directory ldap server. It works fine but seems to be causing problems with the PixelData and the Indexer services, meaning that no pixels data is being written to disk (obviously a big problem).
> 
> I've attached a relevant section of the log file. My password provider is a class without a package, put into extensions.jar along with a ome/services/service-pw.xml file. I know that it's working because it checks passwords as expected and records logins to a log file. Could the problem be that these services use a classpath that doesn't include my jar?
> 
> Any help much appreciated,
> 
> Mark.