Hi, Thanks for the feedback guys.
>> ...1. Logging in through /system/console != /system/sling/login >> >> From what I understand, /system/console is the FELIX admin console login, >> and won't grant you access to modify content. /system/sling/login is the >> JACKRABBIT login page, which will grant you access on updating content.... > > That's correct, the OSGi console uses its own authentication, distinct > from the JCR repository authentication. That explains why it worked OK on one machine and not another. > Sling doesn't use http sessions - when you authenticate via your > browser and later run some javascript code, the browser uses cached > credentials and adds them to the http requests. Do you have any links that detail this, its not something I have heard of before. < insert embarrassed smiley here > Ben 2009/8/13 Bertrand Delacretaz <[email protected]>: > Hi, > > On Thu, Aug 13, 2009 at 3:11 PM, Branden Visser<[email protected]> wrote: >> ...1. Logging in through /system/console != /system/sling/login >> >> From what I understand, /system/console is the FELIX admin console login, >> and won't grant you access to modify content. /system/sling/login is the >> JACKRABBIT login page, which will grant you access on updating content.... > > That's correct, the OSGi console uses its own authentication, distinct > from the JCR repository authentication. > > -Bertrand >
