django-mcauth is a pluggable authentication back-end that lets your users login with their Minecraft.net user/pass.
Requirements
Django 1.2+
Python 2.6 or 2.7 (I don’t care to officially support 2.5)
Installation
Add 'mcauth.backend.MinecraftAuthServerBackend' to your settings.py like so:
AUTHENTICATION_BACKENDS = (
'mcauth.backend.MinecraftAuthServerBackend',
'django.contrib.auth.backends.ModelBackend',
)
If you don’t want to create new local Django users when someone logs in with a valid user/pass, but doesn’t already exist in the DB, you can do this in settings.py:
# Only existing User objects can be authenticated against. MCAUTH_CREATE_UNKNOWN_USERS = False
Support
If you have questions or ideas, or encounter bugs, add an entry to our issue tracker.
License
django-mcauth is licensed under the BSD License.
Metadata
Release files for mcauth 1.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 | Actions |
|---|---|---|---|---|
| mcauth-1.0.tar.gz | 3.7 kB | Without provenance | Details for mcauth-1.0.tar.gz |
Release files / mcauth-1.0.tar.gz
| Download URL | mcauth-1.0.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
458e5677185d2e2b3bb5eb5586e10e9dd683e14860c855b9032e9b5f88ccb9e8
|
|
BLAKE2b-256 checksum How to use checksums |
dfac74e423ef7157c9df2b05e05e9db56cc44e3dee758b238a8fa3669c71bd9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for mcauth 1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.