Ah, I see that it is just the login form. Hadn't thought to try
http://localhost:8080/?sling:authRequestLogin=1
That's fine for now. I guess I'll redirect based on browser.
On Aug 9, 2009, at 8:17 AM, Magnus Johansson wrote:
Hi
Sorry, my memory was not correct... on my system it is
http://localhost:8080/system/sling/login
I'm not running the absolute latest, but I should have code from
beginning
of July.
Regards
Magnus Johansson
On Sun, Aug 9, 2009 at 11:37 AM, Ian Boston <[email protected]> wrote:
Perhaps I am being really dumb this morning, and I can see the html
login
template in the code, but I cant see how to get it invoked.
http://localhost:8080/system/login.html gives a 404 and
grep -rl '/system/login' * on the code base gives no matches.
what's the url, I would like to verify since there might be a bug
with the
way we are dealing with logins.
Ian
BTW, I dont know if its relevant but this part of the code base was
re-factored in the last few months, I am using trunk.
On 9 Aug 2009, at 10:10, Magnus Johansson wrote:
Hi
I've had problems with Safari 4 as well, bu this is only when I'm
using
the
login form under /system/login
(if I remember correctly). It seems the XMLHttpRequest way of
forcing
basic
authentication for
some reason don't work with Safari
However, using ?sling:authRequestLogin=1 on some other URL works
/Magnus
On Sun, Aug 9, 2009 at 11:02 AM, Ian Boston <[email protected]> wrote:
I just tried
http://localhost:8080/?sling:authRequestLogin=1
and got a HttpBasic Auth prompt from Safari 4.0.x and then logged
in
successfully with 'admin' 'admin'
IIRC, you have to add the sling:authRequestLogin=1 to trigger the
basic
auth 401 response from Sling.
Ian
On 9 Aug 2009, at 04:50, Andreas Kollegger wrote:
Hi,
"Apache Sling HTTP Header Authentication" doesn't seem to work
with
Safari
(and I presume other WebKit browsers). Could anyone share some
insight
into
what is wrong, or point me to the relevant JIRA issue? I'm not
familiar
with
the details of http-authentication, so tracing through the code
only got
me
far enough to realize something wasn't happening as expected on
the
browser
side.
Thanks,
Andreas
