Unable to login via certain mobiles [#1484164]

I've seen reports of this happening on both iOS and Andriod.

One cannot log in to the denver site via a mobile device (I've reproduced from an iPhone and iPad).

If you visit drupal.org and sign in and then hit the denver site, things work appropriately, however when going to denver2012.drupal.org/user odd things happen when trying to log in.. it's almost as if there's some crazy autocomplete hitting the username field.. characters you type are slow to appear and clicking "log in" simply doesnt do anything.

Comments

Comment #1

drumm

he/him

NY, US

CreditAttribution: drumm commented 15 March 2012 at 19:54

Can you log in via another subsite, like groups.drupal.org?

Comment #2

ultimateboy CreditAttribution: ultimateboy commented 15 March 2012 at 19:59

Interesting.. I get Access Denied on the path drupal.org/bakery/login when attempting to login to gdo via my iPhone. Still cant log in, but definitely different errors visually.

Comment #3

ultimateboy CreditAttribution: ultimateboy commented 15 March 2012 at 20:08

Just uncovered that what I reported earlier about being able to successfully log in to d.o via mobile safari is incorrect. I get an Access Denied on the /bakery/login path.

This is getting even more curious. coltrane had me try desktop safari logging in to d.o, g.d.o and the denver site.. that uncovered the fact that this is not just mobile. I experience the following when trying desktop safari.

d.o: good to go, can log in fine and visit any sub site and be logged in.
g.d.o: Access Denied on /bakery/login
denver: Access Denied on /bakery/login

It appears that safari and sub sites is having issues which might be propagating itself down to mobile safari.

Comment #4

ultimateboy CreditAttribution: ultimateboy commented 15 March 2012 at 20:22

Project:	DrupalCon Denver 2012 Website	» Drupal.org site moderators
Component:	Code	» Other

As this is no longer just a denver issue, and it effects additional sub sites, moving to the webmasters queue.

Comment #5

coltrane

he/him

CreditAttribution: coltrane commented 15 March 2012 at 20:26

If you are getting 403 on drupal.org/bakery/login make sure you are first logged out of drupal.org by visiting drupal.org/logout

If you still get 403 on drupal.org/bakery/login visit your drupal.org/user page (after logging into drupal.org) and save your account page (you don't need to change anything, just hit save on the page).

Comment #6

Zarabadoo CreditAttribution: Zarabadoo commented 15 March 2012 at 20:36

This seems to be related to a fresh login. I had never previously logged in with my Android device, and it would not log me in. I tried several times to no avail. So I tried it on Drupal.org to see if i was mistaken on credentials. It worked there, so I went back to the Drupalcon site and was logged in. I then logged out and tried again from there. It worked perfectly.

I then decided to try this on my desktop with a browser that I had never logged in to Drupal.org or Drupalcon with. When trying to log into Drupalcon, it would constantly fail. I then logged into Drupal.org, and returned to Drupalcon. Logging out and back in worked as expected.

Comment #7

coltrane

he/him

CreditAttribution: coltrane commented 15 March 2012 at 20:46

I was able to duplicate using Opera. Trying to log into denver2012.drupal.org I received 403 on http://drupal.org/bakery/login

Closed the browser, reopened to try again and it worked fine.

I don't understand this.

Comment #9

mauritsl CreditAttribution: mauritsl commented 20 November 2012 at 21:00

No problems with login on my galaxy S2. Tested both d.o and g.d.o

Comment #10

bertboerland CreditAttribution: bertboerland commented 4 December 2012 at 20:03

so ho we are going to solve this?

first step, make it reproducable. as in ask peopel with different useragents / mobiles to login an dpost results somewhere?

Comment #11

bertboerland CreditAttribution: bertboerland commented 2 July 2013 at 20:03

I was able to reproduce this on on iPhone 4 / wifi. I will use my own proxy next time. I *think* it is caused by the fact that I logged in with the wrong userid/password combination. It might be that the browser actually cached the POST data and showed the wrong page (yes, mobile browsers do cache POST's :-( )