You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Josias Thöny <jo...@wyona.com> on 2006/06/27 12:13:26 UTC

[1.4] disabled logout entry in menu

Hi devs,

Currently the logout entry is disabled in the menu, because there is no
policy.
However, it's possible to call ?lenya.usecase=ac.logout directly.
So I guess the login/logout usecases ignore policies, which probably
makes sense. But how can we re-enable the logout menu-item? 

TIA for any ideas.

Josias



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] disabled logout entry in menu

Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Andreas Hartmann wrote:
> Joern Nettingsmeier wrote:
>> Andreas Hartmann wrote:
>>> Joern Nettingsmeier wrote:
>>>> Andreas Hartmann wrote:
>>>>> Joern Nettingsmeier wrote:
>>>>>
>>>>> [...]
>>>>>
>>>>>>>> can't we just use the mechanisms which are there?
>>>>>>>>
>>>>>>>> add role "session".
>>>>>>>>
>>>>>>>> <world>
>>>>>>>>   <role id="session"/>
>>>>>>>> </world>
>>>>>>> That would mean to open the authoring area for everyone ...
>>>>>> sorry, i just typed the stuff from memory without checking.
>>>>>> what i meant was:
>>>>>> create a new role "session", add world to this role, check for that
>>>>>> role
>>>>>> in the ac.log[in|out] usecases.
>>>>> Yes, I guess I understood it correctly.
>>>>>
>>>>> With the current implementation, if you give the role "session"
>>>>> to the world, you allow everyone to enter the authoring area
>>>>> without logging in.
>>>>>
>>>>> Maybe we should change this behaviour and require the role
>>>>> "visit" for visiting pages. This would allow to assign roles
>>>>> to the world.
>>>> sorry, i wasn't aware that the session role exists already...
>>> No, it doesn't exist :)
>>> I wasn't specific enough, let me rephrase my statement:
>>>
>>> With the current implementation, if you give *any* role
>>> to the world, you allow everyone to enter the authoring area
>>> without logging in.
>>
>> that is unfortunate for huge values of unfortunate.
>> imho this needs to be fixed before a release can happen. what's the
>> rationale behind this behaviour?
> 
> The intention was that you don't have to introduce a special role
> to be able to access pages, i.e. any role would imply that you can
> at least access the page.

ah, ok. let's get rid of it, we have a "visit" role for that.
world can access the usecases, but only accredited users can visit the 
authoring page.

>> can we implement the same security principle as with the usecases for
>> locations?
> 
> Could you explain this a little more detailed?

ignore me. i had misunderstood the way ac works for documents.

-- 
"Open source takes the bullshit out of software."
	- Charles Ferguson on TechnologyReview.com

--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] disabled logout entry in menu

Posted by Andreas Hartmann <an...@apache.org>.
Joern Nettingsmeier wrote:
> Andreas Hartmann wrote:
>> Joern Nettingsmeier wrote:
>>> Andreas Hartmann wrote:
>>>> Joern Nettingsmeier wrote:
>>>>
>>>> [...]
>>>>
>>>>>>> can't we just use the mechanisms which are there?
>>>>>>>
>>>>>>> add role "session".
>>>>>>>
>>>>>>> <world>
>>>>>>>   <role id="session"/>
>>>>>>> </world>
>>>>>> That would mean to open the authoring area for everyone ...
>>>>> sorry, i just typed the stuff from memory without checking.
>>>>> what i meant was:
>>>>> create a new role "session", add world to this role, check for that
>>>>> role
>>>>> in the ac.log[in|out] usecases.
>>>> Yes, I guess I understood it correctly.
>>>>
>>>> With the current implementation, if you give the role "session"
>>>> to the world, you allow everyone to enter the authoring area
>>>> without logging in.
>>>>
>>>> Maybe we should change this behaviour and require the role
>>>> "visit" for visiting pages. This would allow to assign roles
>>>> to the world.
>>> sorry, i wasn't aware that the session role exists already...
>> No, it doesn't exist :)
>> I wasn't specific enough, let me rephrase my statement:
>>
>> With the current implementation, if you give *any* role
>> to the world, you allow everyone to enter the authoring area
>> without logging in.
> 
> that is unfortunate for huge values of unfortunate.
> imho this needs to be fixed before a release can happen. what's the
> rationale behind this behaviour?

The intention was that you don't have to introduce a special role
to be able to access pages, i.e. any role would imply that you can
at least access the page.


> can we implement the same security principle as with the usecases for
> locations?

Could you explain this a little more detailed?
Thanks!

-- Andreas


-- 
Andreas Hartmann
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
andreas.hartmann@wyona.com                     andreas@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] disabled logout entry in menu

Posted by Joern Nettingsmeier <po...@uni-due.de>.
Andreas Hartmann wrote:
> Joern Nettingsmeier wrote:
>> Andreas Hartmann wrote:
>>> Joern Nettingsmeier wrote:
>>>
>>> [...]
>>>
>>>>>> can't we just use the mechanisms which are there?
>>>>>>
>>>>>> add role "session".
>>>>>>
>>>>>> <world>
>>>>>>   <role id="session"/>
>>>>>> </world>
>>>>> That would mean to open the authoring area for everyone ...
>>>> sorry, i just typed the stuff from memory without checking.
>>>> what i meant was:
>>>> create a new role "session", add world to this role, check for that
>>>> role
>>>> in the ac.log[in|out] usecases.
>>> Yes, I guess I understood it correctly.
>>>
>>> With the current implementation, if you give the role "session"
>>> to the world, you allow everyone to enter the authoring area
>>> without logging in.
>>>
>>> Maybe we should change this behaviour and require the role
>>> "visit" for visiting pages. This would allow to assign roles
>>> to the world.
>>
>> sorry, i wasn't aware that the session role exists already...
> 
> No, it doesn't exist :)
> I wasn't specific enough, let me rephrase my statement:
> 
> With the current implementation, if you give *any* role
> to the world, you allow everyone to enter the authoring area
> without logging in.

that is unfortunate for huge values of unfortunate.
imho this needs to be fixed before a release can happen. what's the
rationale behind this behaviour?

can we implement the same security principle as with the usecases for
locations?


-- 
"Án nýrra verka, án nútimans, hættir fortíðin að vekja áhuga."
"Without new works, without the present the past will cease to be of
interest."
        - Ásmundur Sveinsson (1893-1982)

--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] disabled logout entry in menu

Posted by Andreas Hartmann <an...@apache.org>.
Joern Nettingsmeier wrote:
> Andreas Hartmann wrote:
>> Joern Nettingsmeier wrote:
>>
>> [...]
>>
>>>>> can't we just use the mechanisms which are there?
>>>>>
>>>>> add role "session".
>>>>>
>>>>> <world>
>>>>>   <role id="session"/>
>>>>> </world>
>>>> That would mean to open the authoring area for everyone ...
>>> sorry, i just typed the stuff from memory without checking.
>>> what i meant was:
>>> create a new role "session", add world to this role, check for that role
>>> in the ac.log[in|out] usecases.
>> Yes, I guess I understood it correctly.
>>
>> With the current implementation, if you give the role "session"
>> to the world, you allow everyone to enter the authoring area
>> without logging in.
>>
>> Maybe we should change this behaviour and require the role
>> "visit" for visiting pages. This would allow to assign roles
>> to the world.
> 
> sorry, i wasn't aware that the session role exists already...

No, it doesn't exist :)
I wasn't specific enough, let me rephrase my statement:

With the current implementation, if you give *any* role
to the world, you allow everyone to enter the authoring area
without logging in.

-- Andreas


-- 
Andreas Hartmann
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
andreas.hartmann@wyona.com                     andreas@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] disabled logout entry in menu

Posted by Joern Nettingsmeier <po...@uni-due.de>.
Andreas Hartmann wrote:
> Joern Nettingsmeier wrote:
> 
> [...]
> 
>>>> can't we just use the mechanisms which are there?
>>>>
>>>> add role "session".
>>>>
>>>> <world>
>>>>   <role id="session"/>
>>>> </world>
>>> That would mean to open the authoring area for everyone ...
>>
>> sorry, i just typed the stuff from memory without checking.
>> what i meant was:
>> create a new role "session", add world to this role, check for that role
>> in the ac.log[in|out] usecases.
> 
> Yes, I guess I understood it correctly.
> 
> With the current implementation, if you give the role "session"
> to the world, you allow everyone to enter the authoring area
> without logging in.
> 
> Maybe we should change this behaviour and require the role
> "visit" for visiting pages. This would allow to assign roles
> to the world.

sorry, i wasn't aware that the session role exists already... my head is
spinning a bit, i'm getting ready to go on a vacation and there's so
much stuff going on in the office...



-- 
"Án nýrra verka, án nútimans, hættir fortíðin að vekja áhuga."
"Without new works, without the present the past will cease to be of
interest."
        - Ásmundur Sveinsson (1893-1982)

--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] disabled logout entry in menu

Posted by Andreas Hartmann <an...@apache.org>.
Joern Nettingsmeier wrote:

[...]

>>> can't we just use the mechanisms which are there?
>>>
>>> add role "session".
>>>
>>> <world>
>>>   <role id="session"/>
>>> </world>
>> That would mean to open the authoring area for everyone ...
> 
> sorry, i just typed the stuff from memory without checking.
> what i meant was:
> create a new role "session", add world to this role, check for that role
> in the ac.log[in|out] usecases.

Yes, I guess I understood it correctly.

With the current implementation, if you give the role "session"
to the world, you allow everyone to enter the authoring area
without logging in.

Maybe we should change this behaviour and require the role
"visit" for visiting pages. This would allow to assign roles
to the world.

-- Andreas

-- 
Andreas Hartmann
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
andreas.hartmann@wyona.com                     andreas@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] disabled logout entry in menu

Posted by Joern Nettingsmeier <po...@uni-due.de>.
Andreas Hartmann wrote:
> Joern Nettingsmeier wrote:
>> Andreas Hartmann wrote:
>>> Josias Thöny wrote:
>>>> Hi devs,
>>>>
>>>> Currently the logout entry is disabled in the menu, because there is no
>>>> policy.
>>>> However, it's possible to call ?lenya.usecase=ac.logout directly.
>>>> So I guess the login/logout usecases ignore policies, which probably
>>>> makes sense.
>>> Yes, these usecases are matched in the main sitemap above the
>>> authorized pipelines.
>>>
>>>
>>>> But how can we re-enable the logout menu-item? 
>>> I guess we just have to add the usecase policy. Or should we handle
>>> these usecases in a special way, e.g.
>>>
>>>
>>> <usecases xmlns="http://apache.org/cocoon/lenya/ac/1.0">
>>>   ...
>>>   <usecase id="ac.login" protect="false"/>
>>>   ...
>>> </usecases>
>>
>> can't we just use the mechanisms which are there?
>>
>> add role "session".
>>
>> <world>
>>   <role id="session"/>
>> </world>
> 
> That would mean to open the authoring area for everyone ...

sorry, i just typed the stuff from memory without checking.
what i meant was:
create a new role "session", add world to this role, check for that role
in the ac.log[in|out] usecases.



-- 
"Án nýrra verka, án nútimans, hættir fortíðin að vekja áhuga."
"Without new works, without the present the past will cease to be of
interest."
        - Ásmundur Sveinsson (1893-1982)

--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] disabled logout entry in menu

Posted by Andreas Hartmann <an...@apache.org>.
Joern Nettingsmeier wrote:
> Andreas Hartmann wrote:
>> Josias Thöny wrote:
>>> Hi devs,
>>>
>>> Currently the logout entry is disabled in the menu, because there is no
>>> policy.
>>> However, it's possible to call ?lenya.usecase=ac.logout directly.
>>> So I guess the login/logout usecases ignore policies, which probably
>>> makes sense.
>> Yes, these usecases are matched in the main sitemap above the
>> authorized pipelines.
>>
>>
>>> But how can we re-enable the logout menu-item? 
>> I guess we just have to add the usecase policy. Or should we handle
>> these usecases in a special way, e.g.
>>
>>
>> <usecases xmlns="http://apache.org/cocoon/lenya/ac/1.0">
>>   ...
>>   <usecase id="ac.login" protect="false"/>
>>   ...
>> </usecases>
> 
> can't we just use the mechanisms which are there?
> 
> add role "session".
> 
> <world>
>   <role id="session"/>
> </world>

That would mean to open the authoring area for everyone ...


> <usecase id="ac.login">
>   <role id="session"/>
> </usecase>
> <usecase id="ac.logout">
>   <role id="session"/>
> </usecase>
> 
> it avoids having a special case, and that is always worth some extra
> typing imho :)

I don't quite understand the purpose of the "session" role.
IMO we have to allow the logout usecase for the edit+review+admin
roles, don't we?

-- Andreas

-- 
Andreas Hartmann
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
andreas.hartmann@wyona.com                     andreas@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] disabled logout entry in menu

Posted by Joern Nettingsmeier <po...@uni-due.de>.
Andreas Hartmann wrote:
> Josias Thöny wrote:
>> Hi devs,
>>
>> Currently the logout entry is disabled in the menu, because there is no
>> policy.
>> However, it's possible to call ?lenya.usecase=ac.logout directly.
>> So I guess the login/logout usecases ignore policies, which probably
>> makes sense.
> 
> Yes, these usecases are matched in the main sitemap above the
> authorized pipelines.
> 
> 
>> But how can we re-enable the logout menu-item? 
> 
> I guess we just have to add the usecase policy. Or should we handle
> these usecases in a special way, e.g.
> 
> 
> <usecases xmlns="http://apache.org/cocoon/lenya/ac/1.0">
>   ...
>   <usecase id="ac.login" protect="false"/>
>   ...
> </usecases>

can't we just use the mechanisms which are there?

add role "session".

<world>
  <role id="session"/>
</world>

<usecase id="ac.login">
  <role id="session"/>
</usecase>
<usecase id="ac.logout">
  <role id="session"/>
</usecase>

it avoids having a special case, and that is always worth some extra
typing imho :)



-- 
"Án nýrra verka, án nútimans, hættir fortíðin að vekja áhuga."
"Without new works, without the present the past will cease to be of
interest."
        - Ásmundur Sveinsson (1893-1982)

--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] disabled logout entry in menu

Posted by Andreas Hartmann <an...@apache.org>.
Josias Thöny wrote:
> Hi devs,
> 
> Currently the logout entry is disabled in the menu, because there is no
> policy.
> However, it's possible to call ?lenya.usecase=ac.logout directly.
> So I guess the login/logout usecases ignore policies, which probably
> makes sense.

Yes, these usecases are matched in the main sitemap above the
authorized pipelines.


> But how can we re-enable the logout menu-item? 

I guess we just have to add the usecase policy. Or should we handle
these usecases in a special way, e.g.


<usecases xmlns="http://apache.org/cocoon/lenya/ac/1.0">
   ...
   <usecase id="ac.login" protect="false"/>
   ...
</usecases>


-- Andreas

-- 
Andreas Hartmann
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
andreas.hartmann@wyona.com                     andreas@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org