SALClient can't connect to new server #67
Labels
Bug
Issues that report incorrect or undesirable behaviour(s)
Priority: 1
EVENTUAL: A low priority issue that is unlikely to be addressed until the priority increases.
Summary
If a
SALClient
has previously connected to server (i.e. during initialization), connecting to a new server is not possible if the original server required authentication.Steps to reproduce
If
host
requires authentication:What is the current bug behavior?
SALClient
prompts for username and password (irrespective of whethernew_host
requires authentication.What is the expected correct behavior?
No prompt,
SALClient
should simply connect to new host.Possible fixes
This occurs because after a host has been set during initialization,
SALClient.auth_required
has a value determined by this host. WhenSALClient.host
is called a GET request is made (to the new host), and before it is sentSALClient
requests credentials because it thinks it has to authenticate (which is true of GET requests made to the original host but not the new one). This can be fixed by simply settingauth_required = False
whenhost
is set. If this is done,auth_required
can be removed from__init__
.The text was updated successfully, but these errors were encountered: