django-ticketoffice
django-ticketoffice provides one-shot authentication (a.k.a. temporary credentials) utilities for Django. It lets you create and manage tickets that allow users to perform one action on the website. As an example, Django could use it for the “password reset” action, where users authenticate using a temporary token.
Example
Restrict some URL to guests with valid invitation tickets:
from django.conf.urls import patterns, url
from django_ticketoffice.decorators import invitation_required, stamp_invitation
@invitation_required(place=u'louvre', purpose=u'visit')
@stamp_invitation # Mark invitation as used right **after** view execution.
def visit_louvre(request):
ticket = request.cache['invitation'] # Set by `invitation_required`.
return u'Welcome to the Louvre museum {guest}'.format(
guest=ticket.data['first_name'])
urlpatterns = patterns('', url('^louvre$', visit_louvre, name='louvre'))
Create and deliver tickets for this resource:
from django.utils.timezone import now
from django_ticketoffice.models import Ticket
ticket = Ticket(place=u'louvre', purpose=u'visit')
ticket.set_password(u'I love Paris') # Encrypted in database.
ticket.expiry_datetime = now() + timedelta(days=5) # Optional.
ticket.data = {'first_name': u'Léonard'} # Optional.
ticket.save()
credentials = {'uuid': ticket.uuid, 'password': u'I love Paris'}
visit_url = reverse('louvre') + '?' + urlencode(credentials)
django-ticketoffice focuses on authentication. It does not send invitation emails. You may check django-mail-factory about sending emails.
Project status
django-ticketoffice is, at the moment, a proof-of-concept: it delivers basic features in order to create tickets and to use them in views. It works (you can use it), but it may lack some features (ideas are welcome), and it may change (improve) quite a bit. That said, maintainers will take care of release notes and migrations.
See also vision, roadmap and alternatives to get a better overview of project status.
Resources
Documentation: https://django-ticketoffice.readthedocs.org
Code repository: https://github.com/novapost/django-ticketoffice
Bugtracker: https://github.com/novapost/django-ticketoffice/issues
Continuous integration: https://travis-ci.org/novapost/django-ticketoffice
Roadmap: https://github.com/novapost/django-ticketoffice/issues/milestones
Metadata
Release files for django-ticketoffice 0.2
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-ticketoffice-0.2.zip | 25.5 kB | Without provenance | Details for django-ticketoffice-0.2.zip |
Release files / django-ticketoffice-0.2.zip
| Download URL | django-ticketoffice-0.2.zip |
|---|---|
| Size | 25.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
29ef64ce56000395d6f7972629d659cb9f25695bb8a4a019498b4bd13abe8de9
|
|
BLAKE2b-256 checksum How to use checksums |
2294ffc626309ef588f68f5dc1cb17b583c20f4959b1cbd0649a6299b33171b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-ticketoffice 0.2
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.