robotframework / OldSeleniumLibrary

Deprecated Selenium library for Robot Framework
Apache License 2.0
13 stars 3 forks source link

Authentication info not kept during a testcase. Submit Form makes selenium to ask again for password. #8

Closed spooning closed 9 years ago

spooning commented 9 years ago

Originally submitted to Google Code by m.marag... on 11 Oct 2008

What steps will reproduce the problem?

  1. Use apache with LDAP or Basic authentication
  2. Have a cgi-bin that opens a page and use selenium to login to that by entering the username and password into the url (user:pass@⁠http://etc...
  3. Some of the fields in the form are then filled in and the form cofiguration is submitted using the 'Submit Form' Keyword. Then the authentication popup is displayed again instead keeping the authentication info from the previous login.

What is the expected output? What do you see instead?

The expected outcome is to save the form without asking for a password again. Submitting the form is not asking for authentication again when trying it manually.

Had to disable the authentication to make this work

What version of the product are you using? On what operating system?

Latest Selenium library with robot framework 2.0. Tried it on Ubuntu 8.4 and RHEL 4.5. In both cases firefox 2.0 was used.

Please provide any additional information below.

spooning commented 9 years ago

Originally submitted to Google Code by @yanne on 17 Oct 2008

I was not able to reproduce in the simplest of cases. My setup was as follows:

I had a directory 'auth' which I configured to have access protection by basic authentication. I then created a page with form under authentication, and submitting the form redirected to another page under 'auth'.

You probably have a somewhat more elaborate authentication scheme in use. Can you send me relevant parts of you apache2.conf, and some more details of the http request sequence that happens.

spooning commented 9 years ago

Originally submitted to Google Code by m.marag... on 20 Nov 2008

Yes this is true I cannot replicate it again. I believe it was an error with our httpd.conf