Maybe - we are not goin to change our auth methods much - and I would like
to settle the deployment process so it uses one config file and then we
could pluck the auth methods from there -

Paul Brian
07540 456 115
paul@mikadosoftware.com
Guiding you towards Continuous Delivery of software and business value.

On 18 Mar 2013, at 18:31, Philip Schatz <notifications@github.com> wrote:

In rhaptos2/repo/auth.py:

> +                "name": self.name}
> +
> +
> +def after_authentication(authenticated_identifier, method):
> +    """Called after a user has provided a validated ID (openid or peresons)
> +
> +    method either openid, or persona
> +
> +    """
> +    dolog("INFO", "in after auth - %s %s" % (authenticated_identifier, method))
> +    dolog("INFO", "before session - %s" % repr(session))
> +    userobj = get_user_from_identifier(authenticated_identifier)
> +
> +    # set session, set g, set JS
> +    # session update?
> +    if method not in ('openid', 'persona'):

Should these be hardcoded here?

—
Reply to this email directly or view it on
GitHub<https://github.com/Connexions/rhaptos2.repo/pull/91/files#r3417792>
.

-- 


www.mikadosoftware.com

See your software improve with every change.