Django LastPass SAML authenticator
This is a hacky extension to django-saml-service-provider that, instead of onelogin, uses LastPass Enterprise as an IdP.
Installation
Get it from PyPI:
pip install django-lastpass-sp
Example configuration
# Check the LastPass SAML metadata for the bits after '.../login/'
LASTPASS_CONNECTOR_ID = '1234567/abc4'
# This is the certificate given by LastPass
# or LASTPASS_CERTIFICATE if you want the cert in your conf
LASTPASS_CERTIFICATE_FILE = os.path.join(BASE_DIR, 'lastpass.crt')
# Private key, try it like this:
# openssl genrsa > samlsp.key
# or SAML_SP_KEY if you want the key in your conf
SAML_SP_KEY_FILE = os.path.join(BASE_DIR, 'samlsp.key')
# Certificate, try with self-signed:
# openssl req -new -x509 -key samlsp.key -out samlsp.crt -days 365
# or SAML_SP_CERTIFICATE if you want the key in your conf
SAML_SP_CERTIFICATE_FILE = os.path.join(BASE_DIR, 'samlsp.crt')
# Optional!
# Contact info provided in the metadata
SAML_SP_CONTACT_INFO = {
"technical": {
"givenName": "Admin",
"emailAddress": "admin@example.com",
}
}
# Optional!
# Ditto for organization info
SAML_SP_ORGANIZATION_INFO = {
"en-US": {
"name": "acme",
"displayname": 'Acme Inc',
"url": "http://example.com/",
}
}
AUTHENTICATION_BACKENDS = (
# This is just so you don't block yourself out
#'django.contrib.auth.backends.ModelBackend',
# This is the beef
'sp.auth_backend.SAMLServiceProviderBackend',
)
# Optional
# Create new users with admin and/or staff accounts
# Both default to False
LASTPASS_CREATE_ADMIN = True
LASTPASS_CREATE_STAFF = True
Metadata
Release files for django-lastpass-sp 0.1.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-lastpass-sp-0.1.6.tar.gz | 21.0 kB | Without provenance | Details for django-lastpass-sp-0.1.6.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_lastpass_sp-0.1.6-py3-none-any.whl | Python 3 | none | any | Details for django_lastpass_sp-0.1.6-py3-none-any.whl |
| django_lastpass_sp-0.1.6-py2-none-any.whl | Python 2 | none | any | Details for django_lastpass_sp-0.1.6-py2-none-any.whl |
Total release size: 47.0 kB
Release files / django-lastpass-sp-0.1.6.tar.gz
| Download URL | django-lastpass-sp-0.1.6.tar.gz |
|---|---|
| Size | 21.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf2ff104c21e6dab3d36f358b407fc1b49eb2597307fe74a11faa5b4d92e7cd5
|
|
BLAKE2b-256 checksum How to use checksums |
574a346ffd12bb89c6aa225f2c932c6c596563bc2823e45fb2ceaa2531720dbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / django_lastpass_sp-0.1.6-py3-none-any.whl
| Download URL | django_lastpass_sp-0.1.6-py3-none-any.whl |
|---|---|
| Size | 13.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
871f88682a4bf371838feb63a982a9211fce8223b71e886fd750829c8b18a584
|
|
BLAKE2b-256 checksum How to use checksums |
8e6c291265621ade9b8fb0bd7ef12e2b91b8714b106ebd85c65e92d411c6ea98
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / django_lastpass_sp-0.1.6-py2-none-any.whl
| Download URL | django_lastpass_sp-0.1.6-py2-none-any.whl |
|---|---|
| Size | 13.0 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
abd1ff2bd9ceca8e2ab3491e9e7997e1b92061b050d8dfab360d4fe2c05037c4
|
|
BLAKE2b-256 checksum How to use checksums |
250272bb043b9c7b4b20b4ccd4058af0eff00e591422943d6ad400b236ba5bb5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-lastpass-sp 0.1.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.