[ome-devel] Custom authentication backend

[Josh Moore]

Hi Mark,

This sounds like a great plan, and I'm interested to see how it works out. You will need a Spring bean, though. Copy something like:

  http://git.openmicroscopy.org/?p=ome.git;a=blob;f=components/server/resources/ome/services/service-ome.api.IAdmin.xml;h=5af5a262b6dbaa64d8a9b630358cdc963487e3dd;hb=refs/heads/develop

and make sure it is matches the name ome/services/service-*.xml inside of extensions.jar and contains only the reference to your bean. Whatever name you give the bean should be the value for password_provider. E.g.:

  bin/omero config set omero.security.password_provider imperialPasswordProvider

Other info is available under

  http://trac.openmicroscopy.org.uk/omero/wiki/ExtendingOmero

but speak up if we can help with anything.

Cheers,
~Josh

On Feb 4, 2011, at 12:04 PM, Mark Woodbridge wrote:

> Hi,
> 
> I currently patch the server code to perform authentication using a combination of active directory (for most users) and OMERO's database (for the rest). This avoids providing most users with a password just for OMERO. This could conceivably be done by modifying the ldap and jdbc providers but it would be easier for me to write my own PasswordProvider and put it on the server classpath at runtime. This is simple enough, but is there a hook for this to work? I see that I can select a password_provider in omero.properties but I guess I need to declare a spring bean too?
> 
> Any advice would be appreciated as it would mean I don't have to rebuild the server...
> 
> Mark.