The behavior of the M2M API recently changed where if you try to login using an invalid or expired token, there will be an error message. The login will by default supply old tokens to the request with the .usgs file saved in the home folder (when the save argument during login = true). This will result in an error being raised to the end user saying that their authentication has been revoked and with the new change may be more confusing than it's worth if the behavior of the M2M api remains this way.
The behavior of the M2M API recently changed where if you try to login using an invalid or expired token, there will be an error message. The login will by default supply old tokens to the request with the .usgs file saved in the home folder (when the save argument during login = true). This will result in an error being raised to the end user saying that their authentication has been revoked and with the new change may be more confusing than it's worth if the behavior of the M2M api remains this way.