Describe the solution you'd like
The repo is still using code based on the previous 'request' login approach which could get the status code
Selenium does not report back the status code so incorrect user or pwd can not be stopped if the html returns e.g. 404
The conneciton attempt hence continues until the first calls for 'whoami' and 'pce' which then crash.
In between messages of isConnected are thus not true
Suggested
As it is quite complex to achieve via Selenium, add logic from the Whoami onward....whoami to provide the first proof
Describe the solution you'd like The repo is still using code based on the previous 'request' login approach which could get the status code Selenium does not report back the status code so incorrect user or pwd can not be stopped if the html returns e.g. 404 The conneciton attempt hence continues until the first calls for 'whoami' and 'pce' which then crash. In between messages of isConnected are thus not true
Suggested As it is quite complex to achieve via Selenium, add logic from the Whoami onward....whoami to provide the first proof