You are viewing the PKP Support Forum | PKP Home Wiki

OJS - Shibboleth Integration

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.

OJS - Shibboleth Integration

Postby jcmoreira » Fri Jul 18, 2014 5:58 am

Hi !

I've recently been assigned the task to integrate our OJS with a federation using the Shibboleth plugin. However, when we activate and configure the plugin, the "local" login page disappears, and the only authentication method available is the shibboleth one.
Is that the way it was supposed to be? I mean, we wanted to make OJS available to users in the federation, but without closing access to
non-federated users. Is there a way to make this "mixed" auth method, with
the current OJS version?
If not, are there any plans to make it possible?
Posts: 1
Joined: Fri Jul 18, 2014 5:54 am

Re: OJS - Shibboleth Integration

Postby meinbrodt » Mon Sep 29, 2014 4:47 am


we encountered the same behavior. So far it doesn't seem to be possible to allow a single-sign-on for users of your institution using a third party authentication provider and to give external users the possibility to register and authenticate directly with OJS.

I suppose it has something to do with the following point made in this post (viewtopic.php?f=8&t=12164&p=46482&hilit=shibboleth#p46482)

The reason that this is such a sore point is that OJS requires good relational data storage for content attached to users: who reviewed what; who has what role; etc. This means it's necessary for OJS to maintain its own user database for the sake of maintaining a reliable audit trail for the journals. Having that database synchronize against a separate database of some sort introduces a lot of questions about how alignment should be maintained. We haven't managed to determine best practices here.

Regards, Matthias
Posts: 14
Joined: Sun Oct 21, 2012 2:37 am

Return to OJS Development

Who is online

Users browsing this forum: No registered users and 2 guests