On Mon, Oct 27, 2008 at 9:30 AM, Lukasz Szybalski <[EMAIL PROTECTED]> wrote:
>
> On Mon, Oct 27, 2008 at 9:53 AM, Dean Landolt <[EMAIL PROTECTED]> wrote:
>>
>>
>> On Sun, Oct 26, 2008 at 7:09 PM, Lukasz Szybalski <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> On Wed, Oct 22, 2008 at 7:51 AM, Gustavo Narea <[EMAIL PROTECTED]>
>>> wrote:
>>> > Hello,
>>> >
>>> > I think
>>> >
>>> >> Do you need Identity (usernames/passwords) in this project? [no]
>>> >
>>> > should be replaced by
>>> >
>>> >> Do you need authentication and authorization in this project? [yes]
>>> >

totally agreed, we should make this the default.

>>>
>>> What is the difference between required username/pass vs
>>> authentication and authorization?
>>
>> There's two layers to user management -- the who and the what. First, the
>> app has to know who you are (authentication), then it can make the
>> determination of what you're allowed access to (authorization).
>
also username/pass is less professional :)

> So wouldn't the authentication and authorization include identity?
>
they are it's subcomponents, and the main complain we had with tg1
identity was that they where too couple, which is why this approach
was taken, and as usual instead of reinventing the wheel, TG core
looked around and found repoze.who, but since they are only focus on
the authentication part. tg.ext.repoze.who and tg.authorization where
born.

>
> So it seems to me that you guys will try to replace identity with the
> new authorization system?
>
That comment seems to be very outdated, several months ago that was
done with tg.ext.repoze.who :)

> Thanks,
> Lucas
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to