Skip to content

leibniz-psychology/openid

This branch is 152 commits ahead of ulsdevteam/pkp-oauth:master.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

cfee09b · Sep 21, 2022
Jan 4, 2022
Oct 29, 2020
Jan 22, 2021
Sep 6, 2022
Nov 5, 2021
Nov 3, 2021
Mar 3, 2021
Nov 4, 2021
Jun 23, 2022
Nov 4, 2021
Aug 31, 2022
Sep 17, 2020
Nov 3, 2021
Feb 26, 2021
Sep 29, 2020
Sep 29, 2020
Sep 21, 2022
Oct 1, 2020
Jul 19, 2021

Repository files navigation

OJS Plugin for OpenID integration

CI Test

GitHub release (latest by date including pre-releases) GitHub code size in bytes GitHub OJS-Version GitHub All Releases

Übersetzungsstatus

Description:

Currently, PKP's Open Journal System (OJS) does not offer the possibility of OpenID authentication using single sign-on providers. There are also no fully functional community plugins available, which solve this problem. Actually, there is an OAuth plugin that was created in the Fredericton Sprint in 2016, which was ultimately forked into the ORCID plugin. The OAuth plugin is used as basis for the development of this OpenID plugin, because fundamental functions for an authentication like receiving the authentication code and the JSON Web Token (JWT) were available. When the development of this plugin is completed, it will be made available to the PKP community via PKP's plugin gallery and maintained for future OJS versions.

Features:

  • Authentication via OpenID provider, i.e. the local OJS login is completely replaced. To keep the login secure, the JWT is validated via a public key before the user is logged in.
  • Registration of new users via OpenID provider. User data (e-mail, given name, family name, OpenID identifier) is transferred from the Provider to OJS and used for registration.
  • Merge existing user accounts: It is possible to connect existing OJS accounts to the OpenID account. This process must be done by the users themself to keep the administration effort as simple as possible. After the accounts are connected, local login is disabled for these accounts and the users have to authenticate via OpenID.
  • Automatic generation of an OJS-API key to simplify the connection between OJS and third-party software. Currently, users have to generate this key manually, which is very cumbersome in case of developing an inhouse software infrastructure.