AFAIK, the authentication context is only available inside the action protecting a page - which means that all pages must be explicitly protected. You can protect multiple pages within a single protection action, and there is an example in the docs (http://cocoon.apache.org/2.1/developing/webapps/authentication.html in the section "Pipeline Patterns") on how to do it. I haven't started using it yet, but reading the list I believe there is a restriction where the protection can only happen in the sitemap that declares the authentication handler - if you try to use it in a subsitemap you get an error saying it doesn't exist, and if you re-declare it then your users have to log in all over again.
Does anyone know if that's fixed yet, or is it still a TODO? This is something I really need support for RSN so if it's not done, please can someone tell me give me some hints on what to do and I'll get onto it? John -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 07 May 2004 11:39 To: [EMAIL PROTECTED] Subject: RE: HELP! LOSING authentication from session context! Oops, noticed an error in the subject. Hope this makes it clearer. Bye, Helma > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Friday, 07 May 2004 11:04 > To: [EMAIL PROTECTED] > Subject: HELP! using authentication from session context! > > > Hi, > > could someone please help? I built the authentication along > the lines of the various examples, but using flow scripts > instead of actions. All this works well and a > <authentication> section is added to the session context. I > retrieve this with <session:getxml context="authentication" > path="/"/> and a session transformer. > > All this works well... until I suddenly get to a different > page and an error comes along stating that the > "authentication" context is no longer available! I cannot > figure out what happens. It does happen with the same pages > everytime, but some of them follow the same pattern as others > that don't have this problem. > > More specific: > I log in, I get a page to search for a person, login info is > displayed (correct), I select several other pages in the menu > list and they are also correctly displayed. > > I log in, I get a page to search for a person, login info is > displayed (correct), I select "about" or "news" and I get the > above error. If I press "back" and select one of the above > pages, they are displayed correctly. > > I log in, I get a page to search for a person, login info is > displayed (correct), I enter info and press submit, I get the > above error. > > > Bye, > > Helma van der Linden > Medical Informatics > University Maastricht > POBOX 616 > 6200 MD Maastricht > The Netherlands > [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
