Django auth system.
Tested with Django 1.10.4 and Python 3.5.
## Installation guide
First install package using pip
```sh
pip install django-goncord
```
After installation register middleware and authentication backend in settings
```python
MIDDLEWARE_CLASSES = [
...
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django_goncord.middleware.GoncordMiddleware',
...
]
...
AUTHENTICATION_BACKENDS = [
'django.contrib.auth.backends.RemoteUserBackend',
]
```
Then register auth system url parameters in settings
```python
GONCORD = {
'BASE_URL': 'URL like http://www.my-site.ru',
}
```
You can define your own authentication urls
```python
GONCORD = {
...
'VALIDATE_URL': 'SUB_URL like /validate',
'LOGIN_URL': 'SUB_URL like /login',
'LOGOUT_URL': 'SUB_URL like /logout',
'REGISTER_URL': 'SUB_URL like /register',
'UPDATE_PAYLOADS_URL': 'SUB_URL like /update',
'RESET_PASSWORD_URL': 'SUB_URL like /reset_password',
...
}
```
at the end specify Django **LOGIN_URL** parameter
for working with package use **login_required** decorator from **django.contrib.auth.decorators**
For using special methods like **login** import **goncord** from **django_goncord.backends**
## django_goncord.backends.goncord methods
### login(request, data)
provide request for authenticate user
> require: django request object and data for submitting to remote server
### logout(request)
provide request for logout user
> require: django request object
### validate(request)
provide token validation for user on remote server
> require: django request object
### register(data)
provide user registration request
> require: data for submitting to remote server
### reset_password(request, data)
provide password reset for authenticated user
> require: django request object and data for submitting to remote server
all methods return response result from remote server
Metadata
Release files for django-goncord 0.2.6
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-goncord-0.2.6.tar.gz | 3.9 kB | Without provenance | Details for django-goncord-0.2.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_goncord-0.2.6-py3-none-any.whl | Python 3 | none | any | Details for django_goncord-0.2.6-py3-none-any.whl |
Total release size: 9.2 kB
Release files / django-goncord-0.2.6.tar.gz
| Download URL | django-goncord-0.2.6.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
08a142b6349da325b159a63b5074d4d00fa5e33a7487829134f4108cf9741e83
|
|
BLAKE2b-256 checksum How to use checksums |
28139fbb131b26793794ee0bd67a189d8df06157db777743cd57c35885802339
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.7.3 requests-toolbelt/0.9.1 tqdm/4.30.0 CPython/3.6.6
|
Release files / django_goncord-0.2.6-py3-none-any.whl
| Download URL | django_goncord-0.2.6-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8f9786fc48d83032907440fe15288c9ce05093901d5869103b1ebd4b927f36f3
|
|
BLAKE2b-256 checksum How to use checksums |
eceef3f25b61dcd943da1885c8b476e528a849091ad3c31d1e7679a05337f98c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.7.3 requests-toolbelt/0.9.1 tqdm/4.30.0 CPython/3.6.6
|
Security for django-goncord 0.2.6
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.