omniauth :mediawiki, " consumer_key ", " consumer_secret ", If you are using devise, this is how it looks like in your config/initializers/devise.rb: config. use OmniAuth :: Builder do provider :mediawiki, " consumer_key ", " consumer_secret " end php: Method MediaWikiExtensionsOAuthEntityAccessTokenEntity::toString() must not throw an exception, caught LcobucciJWTSignerKeyFileCouldNotBeRead. Once these are in, you need to add the following to your config/initializers/omniauth.rb: Rails. Of course if one or both of these are unreleased, you may have to pull them in directly from github e.g.: gem ' omniauth ', :git => ' ' gem ' omniauth-mediawiki ', :git => ' '
Wikimedia has an OpenID-like extension on top of OAuth (referred to as /identify in later slides) which can do authentication. Not a big difference, but you have to use different libraries/methods. So let's say you're using Rails, you need to add the strategy to your Gemfile along side omniauth: gem ' omniauth ' gem ' omniauth-mediawiki ' () Wikimedia uses OAuth 1.0a most sites these days use OAuth 2.0. Usage is as per any other OmniAuth 1.0 strategy. And on my wiki I have Extension:OAuth2 Client installed.
#MEDIAWIKI OAUTH HOW TO#
MediaWiki uses the OAuth 1.0a extension, you can read about it here: How To Use It I have WPOauthServer running on my WordPress (Wordpress plugin). This gem contains the MediaWiki strategy for OmniAuth. OIDC OpenID Connect is an extension to the OAuth standard that provides for exchanging Authentication data between an identity provider (IdP) and a service.