edc-auth
Authentication for the Edc
Importing users
You create user accounts by importing a specially formatted CSV file. Once an account is created a “Welcome” email may be sent.
Import users from a CSV file with columns:
username
first_name
last_name
job_title
email
alternate_email
mobile
sites: a comma-separated list of sites
groups: a comma-separated list of groupsThen import the users from your application commandline
python manage.py import_users --csvfile=/Users/erikvw/meta_users.csv --notify-to-test-email=ew2789@gmail --resource-name=meta.clinicedc.org --resend-as-newLegacy notes
Important: If you are upgrading from edc_base.auth:
The userprofile table is now in edc_auth. edc_auth has one migration for this table. Copy the same table from edc_base and fake the edc_auth migration.
CREATE TABLE edc_auth_userprofile LIKE edc_base_userprofile;
INSERT edc_auth_userprofile SELECT * FROM edc_base_userprofile;python manage.py migrate edc_auth --fakeYou can now run the edc_base migration safely.
2 maintainers
Metadata
2 maintainers
Release files for edc-auth 0.1.30
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| edc_auth-0.1.30-py3-none-any.whl | Python 3 | none | any | Details for edc_auth-0.1.30-py3-none-any.whl |
Release files / edc_auth-0.1.30-py3-none-any.whl
| Download URL | edc_auth-0.1.30-py3-none-any.whl |
|---|---|
| Size | 60.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9361d347e473c09469afa3b6ab2a3d9bac17f8ed30db8bf97decc63b17efcb04
|
|
BLAKE2b-256 checksum How to use checksums |
d1b9cb527064e381ae0d8fe611905b647fa19dcae2aef7056f5083eac1f81467
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.7.4
|
Security for edc-auth 0.1.30
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.
