Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master
Commits on Jan 20, 2014
  1. Merge pull request #17 from leplatrem/optional_came_from

    authored
    Optional came_from parameter on login/logout
  2. @leplatrem
Commits on Nov 12, 2013
  1. Merge pull request #14 from LostProperty/set_came_from_value_on_query…

    authored
    …string_parameter
    
    Allow setting came_from value with url parameter.
    
    This give more customization options for the forbidden page.
Commits on Nov 11, 2013
  1. @rob-b

    Add example of overriding the pyramid_person forbidden view

    rob-b authored
    Indicate how to either simply use a different template or how to redirect non-authenticated users to the login page
Commits on Nov 10, 2013
  1. Added the missing dependency to MarkupSafe

    authored
    It used to be a dependency of pyramid, but not any more, so it should be state explicitly.
  2. @rob-b

    Allow setting came_from value with url parameter

    rob-b authored
    The current behaviour is to set `came_from` to the value of the current
    url which works well when returning 403 pages. For non-logged in users I
    would prefer to redirect them to the login page (while keeping the 403
    response for logged in users) and so would like to be able to set a url
    parameter which indicates which page to return to.
    
        @forbidden_view_config(renderer='403'.jinja2')
        def forbidden(request):
            if authenticated_userid(request):
                request.response.status = 403
                return {}
            url = request.route_url('login', _query={'came_from': request.path})
            return HTTPSeeOther(url)
    
    With the change to `utils.js` the above works alongside the current
    implementation.
    
    I added an additional setting so that a user can define what querystring
    parameter to use although I default to `came_from`. Feel free to change the
    setting name as I'm not completely happy with it.
Commits on Sep 12, 2013
Commits on Aug 5, 2013
  1. Preparations for release 1.5.

    authored
Commits on Jul 19, 2013
Commits on May 30, 2013
  1. Added `success` to the login view response, to state whether the logi…

    authored
    …n attempt was successful, and whether the user should be considered as logged-in.
Commits on May 23, 2013
  1. Preparations for release 1.4.

    authored
  2. Fixed a bug that caused a crash on python 3.

    authored
    I was erasing the default response headers, which contained the
    encoding. Then caused the json renderer to crash on python 3 because
    webob denied access to response.text.
  3. Added tox config file

    authored
Commits on May 22, 2013
  1. Dropped 3.2 testing from travis because markupsafe dropped it.

    authored
    pyramid_persona is still usable with 3.2 with an older markupsafe
    version
Commits on May 21, 2013
  1. Changed the login call to ajax. This fixes #12.

    authored
    Also changed the login view to return some json containing the address
    to where the user should be redirected. Updated the customization
    process in the docs to take that into account.
    
    Added an example of login customization in the demo.
Commits on Jan 20, 2013
  1. Preparations for release 1.3.1.

    authored
Commits on Jan 19, 2013
  1. Preparations for release 1.3.

    authored
Commits on Dec 24, 2012
  1. Reintroduced dependency to pyramid>=1.4 now it is released.

    authored
    Cleaned up the code accordingly.
  2. Fixed tests.

    authored
  3. Removed the pinned requests version for travis now that the packaging…

    authored
    … problem is fixed in requests.
Commits on Dec 4, 2012
  1. Updated the readme now we have some docs.

    authored
    The docs aren't perfect yet, but now I can extend them without
    bloating my readme. Fixes #9.
  2. Added the docs.

    authored
  3. Switched to a AuthTktAuthenticationPolicy so that the login doesn't e…

    authored
    …xpire with the session. (fixes #7).
Commits on Nov 14, 2012
  1. Preparations for release 1.2.

    authored
Commits on Nov 12, 2012
  1. Updated CHANGES

    authored
Something went wrong with that request. Please try again.