Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
TurboGears Trunk
Home
+ new post
About this group
Join this group
TurboGears 2.2 and authentication
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   4 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Christoph Zwerschke  
View profile  
 More options Sep 17 2012, 1:14 pm
From: Christoph Zwerschke <c...@online.de>
Date: Mon, 17 Sep 2012 19:16:34 +0200
Local: Mon, Sep 17 2012 1:16 pm
Subject: TurboGears 2.2 and authentication
Print | Individual message | Show original | Report this message | Find messages by this author
While upgrading a project from TG 2.1 to 2.2 I noticed that the
"authenticators" setting (a list of custom authenticators) is handled
differently depending on whether "authmetadata" is defined ("new-style
config") or not ("old style").

In new-style configuration, the default authenticator will not be used
at all when custom authenticators are specified, while in old-style
configuration, the default authenticator will be appended.

I think we should re-establish the old behavior. It often makes sense to
prepend additional authenticators to the default one. Of course, you can
always add the default one manually, but it's cumbersome.

Or, we could make it even more flexible by allowing a value of
('default', None) in the "authenticators" list which will be
automatically replaced by the default authenticator. That way you can
specify exactly the position of the authenticator in the chain. I have
already created a patch for this, let me know what you think.

-- Christoph


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Alessandro Molina  
View profile  
 More options Sep 17 2012, 2:54 pm
From: Alessandro Molina <alessandro.mol...@gmail.com>
Date: Mon, 17 Sep 2012 20:54:29 +0200
Local: Mon, Sep 17 2012 2:54 pm
Subject: Re: [tg-trunk] TurboGears 2.2 and authentication
Print | Individual message | Show original | Report this message | Find messages by this author
I'm for the "None" / "default" way, the change was because it sounded
confusing to have the user write a list of authenticators and end up
having a different one. Also disabling the default authenticator was
more complex than it should have been. Going for the default/None way
would provide the best of the two worlds.

As soon as Michael ends moving things to github I think we can merge
the patch and include it in a future 2.2.1 release.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Michael Pedersen  
View profile  
 More options Sep 18 2012, 11:56 pm
From: Michael Pedersen <m.peder...@icelus.org>
Date: Tue, 18 Sep 2012 23:56:31 -0400
Local: Tues, Sep 18 2012 11:56 pm
Subject: Re: [tg-trunk] TurboGears 2.2 and authentication
Print | Individual message | Show original | Report this message | Find messages by this author
On Mon, Sep 17, 2012 at 2:54 PM, Alessandro Molina

<alessandro.mol...@gmail.com> wrote:
> I'm for the "None" / "default" way, the change was because it sounded
> confusing to have the user write a list of authenticators and end up
> having a different one. Also disabling the default authenticator was
> more complex than it should have been. Going for the default/None way
> would provide the best of the two worlds.

> As soon as Michael ends moving things to github I think we can merge
> the patch and include it in a future 2.2.1 release.

No need to wait even. The repositories will be copied wholesale, so
the push can be done whenever. The only things that are being a pain
are the issues themselves, and that just takes time to finish working
through. This week, hopefully.

As for my preference, I like the best of both worlds approach.

--
Michael J. Pedersen
My Online Resume: http://www.icelus.org/ -- Google+ http://plus.ly/pedersen
Google Talk: m.peder...@icelus.org -- Twitter: pedersentg


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Christoph Zwerschke  
View profile  
 More options Sep 19 2012, 4:13 am
From: Christoph Zwerschke <c...@online.de>
Date: Wed, 19 Sep 2012 10:13:12 +0200
Local: Wed, Sep 19 2012 4:13 am
Subject: Re: [tg-trunk] TurboGears 2.2 and authentication
Print | Individual message | Show original | Report this message | Find messages by this author
Am 19.09.2012 05:56, schrieb Michael Pedersen:

> No need to wait even. The repositories will be copied wholesale, so
> the push can be done whenever.

Ok, I'll only have time next week anyway. Will check that in to the
development branch then and merge it back to the branch-2.2 so it will
go to 2.2.1.

-- Christoph


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google