Permalink
Commits on Apr 8, 2013
Commits on Apr 7, 2013
  1. convert emails to utf-8 bytes before hashing, if they are unicode

    This could result in some issues, eg the behavior of default_username_algo  will change subtly from py2 to py3k
    committed Apr 7, 2013
Commits on Apr 5, 2013
  1. remove dependency on unittest2

    This allows support for both python 2.6 and 3.3
    committed Apr 5, 2013
  2. @Osmose

    Fix #146: Support running tests with python setup.py test.

    Removes dependency on Fabric.
    committed with Osmose Apr 5, 2013
Commits on Apr 1, 2013
  1. @willkg

    Fix typo

    willkg committed Apr 1, 2013
Commits on Mar 8, 2013
  1. @willkg

    Issue 138. Fix login failure auto-login

    If you have BROWSERID_CREATE_USER = False, then try to log in with a valid
    account on Persona, but not on the site, then you end up in this endless
    loop of going to a page on the site and being redirected to the login
    failure page immediately.
    
    This fixes that.
    willkg committed Mar 8, 2013
Commits on Mar 5, 2013
  1. @Osmose

    0.8 release, w00t!

    Osmose committed Mar 5, 2013
Commits on Mar 4, 2013
  1. @Osmose

    Fix #97: Raise BrowserIDException on service errors and handle in view.

    - Adds BrowserIDException and updates verify to raise it when there is 
      an issue connecting to the remote verification service.
    - Update the Verify view to catch the raised BrowserIDException and 
      redirect to the login failure page when it is raised.
    Osmose committed Mar 4, 2013
  2. @Osmose
  3. @Osmose
  4. @peterbe

    Merge pull request #134 from Osmose/redirect-security

    Fix #125: Add security checks to Verify view.
    peterbe committed Mar 4, 2013
  5. @Osmose
  6. @Osmose
  7. @Osmose

    Drop support for Django 1.3.

    Osmose committed Feb 26, 2013
  8. @Osmose

    Make browserid_info a function to fix the form CSRF.

    Django's CSRF protection is difficult to use outside of a view. When
    browserid_info was being generated in the context processor, it couldn't
    get the {% csrf_token %} tag to output a CSRF token.
    
    To fix this, we change browserid_info to a function that executes when
    the template is rendered. By that point, the Django CSRF plumbing has
    sorted itself out and {% csrf_token %} now outputs a token correctly.
    This also has the side benefit of making the API a bit more consistent.
    Osmose committed Feb 26, 2013
  9. @Osmose

    Update docs and changelog.

    Osmose committed Feb 26, 2013
  10. @Osmose

    Replace browserid_button with browserid_login and browserid_logout.

    - Move template helpers to helpers.py and replace browserid_button
      with browserid_login and browserid_logout instead.
    - Add login form to browserid_info to avoid issues with having a form 
      tag inside an inline element.
    - Simplify Verify view redirect to look directly for the `next` 
      parameter.
    - Update browserid.js to work with the new single-login form.
    Osmose committed Feb 26, 2013
Commits on Feb 27, 2013
  1. @willkg
  2. @tuxcanfly @willkg
  3. @willkg

    Add Javed to AUTHORS

    willkg committed Feb 27, 2013
  4. @tuxcanfly @willkg

    highlight django code blocks

    tuxcanfly committed with willkg Feb 24, 2013
Commits on Feb 17, 2013
  1. @willkg

    Add trove classifier info

    willkg committed Feb 16, 2013
  2. @peterbe @Osmose

    fix

    peterbe committed with Osmose Feb 15, 2013
  3. @peterbe @Osmose

    and the docs/conf.py

    peterbe committed with Osmose Feb 15, 2013
  4. @peterbe @Osmose

    version number in one place

    peterbe committed with Osmose Feb 15, 2013