Hi, The Sling bundled with CRX 1.4.1 has no support to the 'authRequestLogin' parameter. You need to update CRX following the instructions in this page:
http://dev.day.com/microsling/content/blogs/main/updatecrxqs.html (take a look in the comments before start, things have changed a bit if you're using CRX 1.4.1) If you need further support, I suggest you to try this list, as we may go too out of topic: http://tech.groups.yahoo.com/group/jcr-crx Good luck, Douglas On Mon, Feb 23, 2009 at 07:57, Felix Meschberger <fmesc...@gmail.com> wrote: > Hi Josh, > > Joshua Oransky schrieb: > > I tried that ?sling:authRequestLogin but since anonymous does not have > > read access to that node I get a 404. The problem is even when I log > > into the CRX content explorer with a username that has access to my > > node, I still get a 404 if I try to surf it as this user. How can I make > > the authentication from CRX sticky to the rest of my site? > > Is Safari your browser ? In this case, we have a known issue with the > HTTP Authenticator at the moment, because Safari does not cache the HTTP > Credentials after the XHR request. > > One solution might be to use cookies instead of the standard > authentication header, but I have to admit, this is kind of problematic. > > Regards > Felix > > > > > On Feb 12, 2009, at 1:06 AM, Douglas José wrote: > > > >> ?sling:authRequestLogin > > > > > > -- Douglas Jose http://douglasjose.com - "Use free software. Help us make a free world."
