flask-mwoauth
Flask blueprint to run OAuth against MediaWiki's extension:OAuth.
Note: The python-mwoauth library is more actively maintained, and also contains basic flask support. Please consider using
python-mwoauthdirectly if it supports your use case.
The blueprint adds these uris:
- /login - runs the OAuth handshake and returns the user to /
- /login?next=/someurl will return the user to /someurl
- /logout - clears the users' access tokens
- /logout?next=/someurl will return the user to /someurl
- /oauth-callback - callback from MW to finish the handshake
The users' OAuth key and secret are stored in the session.
In addition, flask-mwoauth adds a few convenience functions:
-
get_current_user(cached=True)reports who the current user is. To confirm the user is still logged in (e.g. tokens have not been revoked), call it with cached=False. -
request(api_query)submits an request through the API, using the users' access tokens. For instance,
result = request({'action': 'query', 'meta': 'userinfo'})
fetches https://www.mediawiki.org/w/api.php?action=query&meta=userinfo and returns the result as Python dict, e.g.
{u'batchcomplete': u'', u'query': {u'userinfo': {u'id': 31344, u'name': u'Valhallasw'}}}
If you are authorized to access other wikis (e.g. en.wikipedia.org, although you authorized via mediawiki.org), you can run a request there using
result = request({'action': 'query', 'meta': 'userinfo'}, url='https://en.wikipedia.org/w/api.php')
For more information on using the api, please check the api documentation at https://www.mediawiki.org/wiki/API:Main_page
The example app
An example app is implemented in demo.py.
- Go to https://meta.wikimedia.org/wiki/Special:OAuthConsumerRegistration/propose and fill in the following values:
- Application name: test app
- Application description: test app for flask-mwoauth
- OAuth "callback" URL: http://localhost:5000/oauth-callback
- Contact email address:
- Leave all other values default.
- Click 'Propose consumer'. You now get a message stating
Your OAuth consumer request has been received.
You have been assigned a consumer token of and a secret token of . Please record these for future reference."
-
Then
$ python setup.py develop $ python demo.py NOTE: The callback URL you entered when proposing an OAuth consumer probably did not match the URL under which you are running this development server. Your redirect back will therefore fail -- please adapt the URL in your address bar to http://localhost:5000/oauth-callback?oauth_verifier=...etc Consumer key: <the consumer key you got> Consumer secret: <the consumer secret you got>You may need to re-enter the key and secret if the app reloads.
-
Go to http://localhost:5000/ and click 'login'.
Projects using flask-mwoauth
To see how flask-mwoauth is used in applications, you can take a look at:
Metadata
Release files for flask-mwoauth 0.4.82
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| flask-mwoauth-0.4.82.tar.gz | 7.7 kB | Without provenance | Details for flask-mwoauth-0.4.82.tar.gz |
Release files / flask-mwoauth-0.4.82.tar.gz
| Download URL | flask-mwoauth-0.4.82.tar.gz |
|---|---|
| Size | 7.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5a6bda17e6ec9a0523ae54cd8c3af844613949712a47d4f2032c50e30a208c14
|
|
BLAKE2b-256 checksum How to use checksums |
ed1c5ad8b2a001f7ceeb8775007577ae196db2c4facc88ff2e60ec8fb86afcfd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.1.0 requests-toolbelt/0.9.1 tqdm/4.33.0 CPython/3.6.7
|
Security for flask-mwoauth 0.4.82
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.