Client token writing is inconsistent #62
Labels
Bug
Issues that report incorrect or undesirable behaviour(s)
Priority: 2
NORMAL: A task which is not critical and should be addressed when there are no higher priority issue
Summary
If the
SALClient
authenticates by simply callingauthenticate
, the received token is assigned toSALClient.auth_token
, but is not written to a file.By contrast, if a
SALClient
which has not previously authenticated callslist
ofget
then as well as authenticating, the token is written to a file.Possible fixes
I think it would make sense to move the token writing (
_write_auth_token
) insideSALClient.authenticate
and write the token by default using awrite_token=True
parameter. Thenwrite_auth_token
can be removed from_make_request
, which already callsauthenticate
.The text was updated successfully, but these errors were encountered: