Compatible with DokuWiki
Similar to authgoogle
The development of this plugin has been sponsored by Linuxhotel.
After setup, you have to select
oauth in the authtype config option.
Please note: this plugin requires two small bugfixes in the Ponder Stibbons release:
The plugin currently supports the following auth providers:
More can easily be added (see development section below)
To be able to use one of those providers you need to create an “Application” at the authentication provider's developer website. The URLs to those are linked in the configuration manager.
The setup of these “Applications” differs between the different providers, but there are a few things you generally need to provide to create one:
Once the application is set up it will display a “key” and a “secret”. These have to be set up in the configuration manager. Once done the service can be used for login.
Do not forget to fill informations into “APIs & auth / Consent screen”. If you don't, the client authentification request will display “Error, no application name”.
This plugin sits on top of the usual authplain authentication mechanism. Password based logins will continue to work and users can still register directly at your wiki, unless you configure it otherwise.
However, the plugin introduces one limitation: email addresses have to be unique for each user. When you're switching from
oauth make sure existing users have unique email addresses!
When a new user logs in through one of the configured oAuth providers a standard user entry is created and associated with the oAuth provider. Additional providers can be enabled in the user's profile (Associations are simple group memberships).
Users can login through any of the services enabled in their profile - for that to work, their email address configured in DokuWiki must match with the primary address known to the service.
Please note: this plugin will never support login via Twitter because Twitter doesn't give access to the user's email address.
This plugin comes with a few predefined services. In the backend it uses the Lusitanian PHPoAuthLib which supports many more services. However each service needs it's own Adapter class which implements the specific API calls to request user data over an oAuth authenticated connection.
Pull Requests for implementing more public services are welcome!
This plugin can easily integrate with your own service. A “Generic” backend class allows for easy configuration of endpoints. However the actual API call for fetching user data still needs to be implemented. The plugin comes with an example Adapter class called “Doorkeeper” which implements oAuth against the demo setup of the Ruby oAuth library Doorkeeper.
To implement your own service, simply copy the Doorkeeper class and adjust the implementation and add the right config values to your config.