DEPRECATED: phovea_security_flask
Security manager implementation based on Flask-Login. Additionally, a login module is provided that can be used at client-side.
DEPRECATION Information
Please note that this project has been archived and is no longer being maintained. There is an active development under https://github.com/datavisyn/tdp_core and we will also contribute our future changes to it.
Installation
git clone https://github.com/phovea/phovea_security_flask.git
cd phovea_security_flask
npm install
Testing
npm test
Building
npm run build
Default users
| Username | Password |
|---|---|
| admin | admin |
| sam | sam |
Add new users
Config File
New users are added to phovea_security_flask/config.json.
The python script encryptor.py hashes a given password and prints password, salt, and hashed password.
Environment Variables
Alternatively, you can provide users via environment variables:
The UserStore class in phovea_security_flask/dummy_store.py reads all environment variables starting with PHOVEA_USER_ and uses the remainder of the enviroment variable key as username. The environment variable's key has to contain: SALT;HASHED_PW;ROLE1 (multiple roles can be added by seperating them with a semicolon), e.g.:
export PHOVEA_USER_bruce.banner="08c52b567cb947c98be6de6e9ad3919f;2c946ca1b8574d506ee5e7b3b22e350bc8c93b9df647d17e4429e727529c63a62d1fb274ca5a7499bd33c0844e437631728ee9fcba14b41204f21ec8cda523f7;avenger;scientist
Defines the following user:
- Username:
bruce.banner - Salt:
08c52b567cb947c98be6de6e9ad3919f - Hashed password:
2c946ca1b8574d506ee5e7b3b22e350bc8c93b9df647d17e4429e727529c63a62d1fb274ca5a7499bd33c0844e437631728ee9fcba14b41204f21ec8cda523f7 - Roles:
avenger, scientist
NOTE: User credentials defined as environment variables override all users defined in the config.json. This behaviour can be used to define development users inside the config.json, and provide users for production via environment variables when deployed.
This repository is part of Phovea, a platform for developing web-based visualization applications. For tutorials, API docs, and more information about the build and deployment process, see the documentation page.
Metadata
Release files for phovea-security-flask 9.0.0
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 | |
|---|---|---|---|---|
| phovea_security_flask-9.0.0.tar.gz | 7.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| phovea_security_flask-9.0.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 15.2 kB
Release files / phovea_security_flask-9.0.0.tar.gz
| Download URL | phovea_security_flask-9.0.0.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
40f41c54bf24e6d08b294e98a31f50e49ca1f1e7e1518d78ed4092026466f146
|
|
BLAKE2b-256 checksum How to use checksums |
481e48dbf293c86ee8c844b9ed9bdc3ddb70969c0eb0ad9cecef4fa50b87dde1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.7.12
|
Release files / phovea_security_flask-9.0.0-py2.py3-none-any.whl
| Download URL | phovea_security_flask-9.0.0-py2.py3-none-any.whl |
|---|---|
| Size | 8.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
49bf041c0249558c7d5146dfb6f801cb3e3c53b9c6831f57ac3e2347f88d47fd
|
|
BLAKE2b-256 checksum How to use checksums |
5226c2dec770bf403b72732eb271f14f9b533dcfa5c1caed316a3dffcb3d7235
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.7.12
|
Security for phovea-security-flask 9.0.0
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.