Menu
▾
▴
#41 login page cycling
Summary of discussion about the login page cycling problem.
> From: Matthew Buckett
>
> Paul Trafford wrote:
>> Hi,
>>
>> David Rischmiller had various problems logging into
WebLearn this
>> morning which I've observed looking over his
shoulder. On a PC with
>> Win XP, he initially tried Firefox: he entered a
specific WebLearn
>> url into the address box, typed in username,
password in login page
>> and got the next page. But clicking on 'Enter Web
site' he got
>> returned to the login page and re-entering his
details did exactly
>> the same.
>
> I have seen this before but have never been able to
reproduce it.
> Whenever I have attempted to login the second time it
all worked.
>
>> He thought is might be cookies, but they were set to
be allowed.
>>
>> Then he tried IE, just clicking on the WebLearn link
on the OUCS home
>> page. He got the page telling him about redirection
and never moved
>> on.
>
> Can anyone reproduce any of these errors?
>
>> He finally got through by entering
>> http://www.weblearn.ox.ac.uk/bodington/site/
>> but got an alert on every page asking whether he
wanted to allow
>> scripts to be run.
>>
>> So prob need more testing on platforms with varying
levels of cookie
>> and script settings, to at least aim for more
predictable behaviour!
>
> I doesn't seem to be related to JavaScript as I can
login sucessfully
> with JavaScript turned off.
----
I've seen something similar, whereby you login and it
takes to the error page. Then you refresh the page and
it takes you straight in.
It seems to cache the username/password coz the
Authenticator gets called every time you access a page.
If you're already authenticated it just returns true
but if you're not, it tries to authenticate you. Very
very painful if you enter the wrong password for LDAP!
Could be that the Authenticator failed for some reason
but succeeded on the next page access.
Another problem I've had is if I stop the server while
I'm logging and the cookie goes to pot. The next time I
login, I get put on the page the cookie says I was on
last, only it's completely stuffed up
(bs_template_login_page4.html) or something.
The cookie is a real problem. It doesn't work on a
public access machine. When you login, you get taken to
the last page the last user was on and as you don't
have their access rights, you get a blank page!
Alistair
---
Bodington usually goes into https for the login and
then back to http on entering the 'website'. It sounds
like a problem with certificates. Is there a proxy of
some kind between your user and the Bodington server?
Aggie
----
Think it must be something other than that Aggie, as we
get the problem on Bodington Common without the secure
login....
Paul
----
We've seen it in the faculty and we thought that it was
a bug in a particular version of IE6, because when we
changed the IE6 to an earlier version, the problem went
away. However, we've never really pinned down what
caused it. I'll have a word with our IT support guys -
they may have done more work on it.
I hadn't spotted that you aren't using the secure login
on Bodington Common.
Aggie
