search

TACC-Cloud / agave-cli

The Tapis CLI
Other
4 stars 8 forks source link

auth tokens do not refresh #2

Closed alejandrox1 closed 6 years ago

alejandrox1 commented 6 years ago

Many commands require a valid oauth token to be present in the Agave configuration file ($HOME/.agave/current). If this is not the case, and the user has already created a client, the tokens should auto-refresh by default. This is not the case, for example:

 $ tenants-list 
Token has expired. Automatically refreshing...
3dem
agave.prod
araport.org
designsafe
iplantc.org
irec
sd2e
sgci
tacc.prod
vdjserver.org
jochoa at jochoa-5520 in ~/Documents/origami/testing_grounds/TACC-Cloud/agave-cli/agave-cli/bin on develop [!?]
 $ tenants-list 
Token has expired. Automatically refreshing...
3dem
agave.prod
araport.org
designsafe
iplantc.org
irec
sd2e
sgci
tacc.prod
vdjserver.org
jochoa at jochoa-5520 in ~/Documents/origami/testing_grounds/TACC-Cloud/agave-cli/agave-cli/bin on develop [!?]
 $ auth-check 
Token has expired. Automatically refreshing...

jochoa at jochoa-5520 in ~/Documents/origami/testing_grounds/TACC-Cloud/agave-cli/agave-cli/bin on develop [!?]
 $ auth-tokens-refresh 
{"error":"invalid_grant","error_description":"Provided Authorization Grant is invalid."}