Fake user is poorly named - will best whip it out and replace with constant
- probably RemoteUser.  It is the wsgi debug user approach (iirr) - ie if
you present that header and its in debug mode you are logged in as that
user with not auth step

Paul Brian
07540 456 115
paul@mikadosoftware.com
Guiding you towards Continuous Delivery of software and business value.

On 18 Mar 2013, at 18:32, Philip Schatz <notifications@github.com> wrote:

In rhaptos2/repo/auth.py:

> +    .. todo::
> +       session assumes there will be a key of 'authenticated_identifier'
> +
> +    .. todo::
> +       I always go and look this up - decide if this is sensible / secure
> +
> +    .. todo::
> +       use secure cookie
> +
> +    I really need to think about session cookies. Default for now.
> +
> +
> +    ..  todo:: document fajkeuserID
> +    '''
> +    dolog("INFO", "Whoami called", caller=whoami)
> +    if "X-Cnx-FakeUserId" in request.headers and app.debug is True:

Were you unable to move to the WSGI-debug-user solution? Could you add a
comment here on what this X-Cnx-FakeUserId is for?

—
Reply to this email directly or view it on
GitHub<https://github.com/Connexions/rhaptos2.repo/pull/91/files#r3417829>
.

-- 


www.mikadosoftware.com

See your software improve with every change.