1. HTTP authentication in
automated testing – problems
and solutions
Igor Cernopolc
Endava
igor.cernopolc@gmail.com

3. Usage
 Intranet portals
 Back office applications
 Cross domain authentication (basic)

4. Main problems
 Non – HTML dialog

5. Main problems
 Non – HTML dialog
Different interface/implementations
along the browsers

6. Main problems
 Non – HTML dialog
Different interface/implementations along the
browsers
Consequence?

7. Consequence
Lots of workarounds for
handling authentication
dialogs during automated
web testing

8. Solutions
Brow Passing the username/password
ser in the HTTP request
based (http://user:pass@domain.com)
Browser
based

9. Solutions
Brow Passing the username/password
ser in the HTTP request
based (http://user:pass@domain.com)
Brow
Browser
ser Firefox profiles
based
based

10. Solutions
Brow Passing the username/password
ser in the HTTP request
based (http://user:pass@domain.com)
Brow
Browser
ser Firefox profiles
based
based
Brow
ser Setting the appropriate
cookie
based

11. Solutions
Brow
ser Firefox AutoAuth addon
based
External

12. Solutions
Brow
ser Firefox AutoAuth addon
based
Brow
External ser java.awt.Robot class
based

13. Solutions
Brow
ser Firefox AutoAuth addon
based
Brow
External ser java.awt.Robot class
based
Brow
ser Autoit, Siculi scripts
based

16. My Solution
 Webdriver
 Java

17. My Solution
 Webdriver
 Java
+
 AutoitX

18. My Solution
 Webdriver
 Java
+ =
 AutoitX

19. My Solution

20. My Solution

21. My Solution

22. My Solution

23. My Solution

25. My Solution

26. My Solution

27. My Solution

28. Limitations
 Windows based
 Selenium Grid

29. Limitations
 Windows based → Siculi?
 Selenium Grid → .exe script based calls?
→ duplicate workspace?

30. Conclusions
Don’t be afraid of using multiple tools
when it is required. Combine and innovate and
you will succeed.

31. Thank you
Please don’t forget to fill in the evaluation form 

32. Diamond Sponsors
Platinum Sponsors Gold Sponsors
Training Partners Media Partners Other Partners