# Introduction
Application for getting, storing and refreshing OAuth access_tokens for Django standalone applications without user manipulations. Applications also can imitate authorized requests on behalf of user
# Providers
## Vkontakte
OAUTH_TOKENS_VKONTAKTE_CLIENT_ID = ‘’ # application ID OAUTH_TOKENS_VKONTAKTE_CLIENT_SECRET = ‘’ # application secret key OAUTH_TOKENS_VKONTAKTE_SCOPE = [‘wall’, ‘friends’] # application scope OAUTH_TOKENS_VKONTAKTE_USERNAME = ‘’ # user login OAUTH_TOKENS_VKONTAKTE_PASSWORD = ‘’ # user password OAUTH_TOKENS_VKONTAKTE_PHONE_END = ‘’ # last 4 digits of user mobile phone
OAUTH_TOKENS_FACEBOOK_CLIENT_ID = ‘’ # application ID OAUTH_TOKENS_FACEBOOK_CLIENT_SECRET = ‘’ # application secret key OAUTH_TOKENS_FACEBOOK_SCOPE = [‘offline_access’] # application scope OAUTH_TOKENS_FACEBOOK_USERNAME = ‘’ # user login OAUTH_TOKENS_FACEBOOK_PASSWORD = ‘’ # user password
# Settings
OAUTH_TOKENS_HISTORY = True # to keep in DB expired access tokens
# Dependencies
django
requests
requests_oauthlib
django-taggit
beautifulsoup4
In order to test with quicktest.py, you also need:
mock
factory_boy
Metadata
Release files for django-oauth-tokens 0.6.3
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 |
|---|---|---|---|---|
| django-oauth-tokens-0.6.3.tar.gz | 46.1 kB | Without provenance | Details for django-oauth-tokens-0.6.3.tar.gz |
Release files / django-oauth-tokens-0.6.3.tar.gz
| Download URL | django-oauth-tokens-0.6.3.tar.gz |
|---|---|
| Size | 46.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fcf9cdea77dc2680b1e79f37afb7b7be18a1b89656cad6f5e2835d4ab1b20d21
|
|
BLAKE2b-256 checksum How to use checksums |
d0fd9c69653a9897b2d98baf9cf3e33af23753d6f33bf669999611f46cabcb10
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-oauth-tokens 0.6.3
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.