On 13 October 2010 17:16, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 10/11/2010 08:21 PM, Laurence Rowe wrote:
>> I'm currently implementing single sign on across Plone sites but have
>> run into a bit of an issue with the CookieAuthHelper.
>>
>> Unauthorized acces
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/11/2010 08:21 PM, Laurence Rowe wrote:
> I'm currently implementing single sign on across Plone sites but have
> run into a bit of an issue with the CookieAuthHelper.
>
> Unauthorized accesses are redirected to its login_path attribute even
> wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/11/2010 08:21 PM, Laurence Rowe wrote:
> I'm currently implementing single sign on across Plone sites but have
> run into a bit of an issue with the CookieAuthHelper.
>
> Unauthorized accesses are redirected to its login_path attribute even
> wh
Am 12.10.2010, 02:21 Uhr, schrieb Laurence Rowe :
> Yet another option would be to let logged in unauthorized to percolate
> up and implement that page with an error view.
> Any opinions? I'm leaning towards adding an insufficient_privs_path as
> it seems simplest and least invasive. (When not set
On 12 October 2010 08:39, Wichert Akkerman wrote:
> On 10/12/10 02:21 , Laurence Rowe wrote:
>>
>> I'm currently implementing single sign on across Plone sites but have
>> run into a bit of an issue with the CookieAuthHelper.
>>
>> Unauthorized accesses are redirected to its login_path attribute e
On 10/12/10 02:21 , Laurence Rowe wrote:
> I'm currently implementing single sign on across Plone sites but have
> run into a bit of an issue with the CookieAuthHelper.
>
> Unauthorized accesses are redirected to its login_path attribute even
> when a user is already logged in. Plone works around t
