This uses django-agent-trust to add OTP-based machine authorization to django-otp.
See django-otp for more information on the OTP framework.
This version is supported on Python 2.6, 2.7, and 3.3+; and Django >= 1.4.
This is technically a Django app, but only for testing purposes. To use this project, just make sure you have django-otp and django-agent-trust installed correctly.
This package provides subclasses of
OTPTokenForm with an extra boolean field called
otp_trust_agent. The user can check this option to indicate that they’d
like to bypass OTP verification when accessing the site from the same browser
in the future.
When these forms are used with
django.contrib.auth.views.login(), we will
call the appropriate django-agent-trust APIs automatically. If the trust option
is selected, the agent will be trusted persistently; if not, it will be trusted
for the current session. Views willing to accept a trusted agent in lieu of OTP
verification may then use
trusted_agent_required() in place of
OTPAuthenticationForm(request=None, *args, **kwargs)¶
OTPAuthenticationFormwith support for agent trust.
If you use any OTP-aware authentication forms that are not
trusted-agent-aware, then the following decorator may be useful. For example,
suppose you have one view protected by
otp_required() and another that is protected by
trusted_agent_required(). If an
authenticated user visits the first view, he will be asked to provide an OTP
token via the standard
OTPTokenForm, which will
verify the user, but will not set up a trusted agent. If he then visits the
second view, he will be asked to verify again, this time with the
OTPTokenForm. This is clearly not
what you intend, since OTP verification should be more than sufficient to
authorize the user for the second view.
To get around this, the following decorator effectively merges
trusted_agent_required() into a single
decorator that will be satisfied with either a verified user or a trusted agent.
The default behavior is to act exactly like
to enable the more lenient policy.
otp_required(view=None, redirect_field_name=u'next', login_url=None, if_configured=False, accept_trusted_agent=False)¶
otp_required(), but with an extra argument.
Parameters: accept_trusted_agent (bool) – If
True, we’ll accept a trusted agent in lieu of OTP verification. Default is
This is an
OTPAdminSitesubclass that is satisfied by a trusted agent.
This is identical to
django_otp.admin.OTPAdminSiteexcept that it will skip the login dialog if the user is already logged in and is either verified with an OTP device or is coming from a previously trusted agent.
AdminSitelacks the hooks necessary to properly implement a trusted agent login form here. If the user does not meet the criteria above, they will have to verify themselves with an OTP device to log in. The experience will be better if you send users through your own custom login flow before redirecting them to this admin site.
Copyright (c) 2012, Peter Sagerson All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.