You are viewing the PKP Support Forum | PKP Home Wiki

Modifying authentication behaviour

OJS development discussion, enhancement requests, third-party patches and plug-ins.

Moderators: jmacgreg, btbell, michael, bdgregg, barbarah, asmecher

Forum rules
Developer Resources:

Documentation: The OJS Technical Reference and the OJS API Reference are both available from the OJS Documentation page.

Git: You can access our public Git Repository here. Comprehensive Git usage instructions are available on the wiki.

Bugzilla: You can access our Bugzilla report tracker here.

Search: You can use our Google Custom Search to search across our main website, the support forum, and Bugzilla.

Questions and discussion are welcome, but if you have a workflow or usability question you should probably post to the OJS Editorial Support and Discussion subforum; if you have a technical support question, try the OJS Technical Support subforum.

Modifying authentication behaviour

Postby selahi » Thu Feb 28, 2008 2:19 am

Dear All,

I want your kind help to modify the basic user authentication behaviour of OJS.

We have a Contact Management System within our organisation based on MsSQL server. We want all our userbase (from journal and other activites) in MsSQL database. Users will use OJS's registration interface to register with the FBA. This interface will be connected to MsSQL server instead of OJS's MySQL DB. Same would be true for Editing profile etc. However, all other details will still be kept in MySQL DB. So, We want OJS to base on two databases MsSQL for users and MySQL for Journal activities (manuscript, journals etc)

Should I be developing a Plugin like Ldap to handle authentication, creation, deletion etc and Loadhandler hook to use this plugin?

What do you say?

Best regards,

Salman Elahi
Posts: 31
Joined: Mon Nov 20, 2006 9:09 am

Re: Modifying authentication behaviour

Postby asmecher » Tue Mar 04, 2008 11:29 am

Hi Salman,

I'd suggest using an authentication plugin if at all possible -- it'll depend on the exact behavior you want out of the system. If that doesn't work, use a generic plugin. I'm in the process of cleaning the proprietary code out a generic plugin that was used by one client to authenticate against a legacy system; while its scope was more limited than you probably had in mind (it was just used to bypass subscription checks), perhaps it will help.

Alec Smecher
Public Knowledge Project Team
Posts: 10015
Joined: Wed Aug 10, 2005 12:56 pm

Return to OJS Development

Who is online

Users browsing this forum: No registered users and 1 guest