How to resolve ClientError.AuthenticationFailed?

[forsyth2]

If you're running into an ClientError.AuthenticationFailed error, you may just need to run rm ~/.globus-native-apps.cfg and rerun zstash. See #322 for more details.

[forsyth2]

Note for testing zstash: This doesn't seem to be sufficient when running python -m unittest tests/test_globus.py

The test was hanging on zstash create.

I ran rm ~/.globus-native-apps.cfg and then python -m unittest tests/test_globus.py again. It asked for an authentication code, but then still hung.

I then ran the steps from #304 (comment) to do a manual test. That asked me for a new authentication code.

I then reran python -m unittest tests/test_globus.py and it worked. Presumably the test code isn't passing on the authentication prompt to the user in all cases...

[forsyth2]

The problem of not being able to automate workflows anymore (because of the authentication prompt) is becoming increasingly common. I ran into the issue on E3SM Data Docs as well -- resolved with E3SM-Project/e3sm_data_docs#34 (comment).

[forsyth2]

Similar fix at #326 (comment) to authenticate outside of an automated script.