Alfresco custom JDBC authenticator

It is designed for users integration between an Alfresco repository and a custom application. You can use it with any type of database (mysql, postgresql, oracle....) with its corresponding jdbc driver and it is fully customizable through authentication properties. You can also use CIFS with this authentication if your password field is stored in MD4.

Installation guide:

The installation is tracked via AMP package. Stop Alfresco, copy the file in ${ALF_HOME}/amps and use ${ALF_HOME}/bin/apply_amps script to install de AMP. Then copy configuration files to the extension directory:


zylk@alf:/opt/alfresco34/tomcat/shared/classes/alfresco/extension/subsystems/Authentication/jdbc/myjdbc/jdbc-authentication-context.xml
zylk@alf:/opt/alfresco34/tomcat/shared/classes/alfresco/extension/subsystems/Authentication/jdbc/myjdbc/jdbc-authentication.properties


In alfresco-global.properties, an example of authentication chain can be:


authentication.chain=alfrescoNtlm1:alfrescoNtlm,myldap:ldap,myjdbc:jdbc


It is important to note that the other CIFS-able subsystems must be deactivated (only one of the subsystems can use CIFS - in fact the first one in the chain). In alfresco-global.properties


alfresco.authentication.authenticateCIFS=false
passthru.authentication.authenticateCIFS=false


An example of custom properties are:


jdbc.driver=org.gjt.mm.mysql.Driver
jdbc.username=root
jdbc.password=secret
jdbc.name=mydb
jdbc.url=jdbc:mysql://localhost:3306/mydb
jdbc.query=SELECT password FROM myusers WHERE id='{1}'

# Default administrators
jdbc.authentication.defaultAdministratorUserNames=zylk,mysql

# CIFS
# If jdbc.authentication.cifs.active = true set jdbc.authentication.password.type = md4
jdbc.authentication.cifs.active=true

# Password storage / encryption type in DB: plain|md5|md4|DES|jcrypt
jdbc.authentication.password.type=md4

And finally, restart your Alfresco instance.