You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 28, 2024. It is now read-only.
calling ./myprovider.sh auth will generate a ./.cookie file, then execute another command (eg get-self), response 401 Authorization Required, then I manually add the access_token to -H 'Authorization: Bearer $access_token ', request again, can work normally (Amazon server Linux).
my improvement is: extract access_token from the response 'cookie' and save it to the ./.access_token file. When executing other commands, read the access_token in the file and put it into -H "Authorization: Bearer $access_token", then send the request.
calling
./myprovider.sh auth
will generate a./.cookie
file, then execute another command (egget-self
), response401 Authorization Required
, then I manually add the access_token to-H 'Authorization: Bearer $access_token '
, request again, can work normally (Amazon server Linux).my improvement is: extract
access_token
from the response 'cookie' and save it to the./.access_token
file. When executing other commands, read theaccess_token
in the file and put it into-H "Authorization: Bearer $access_token"
, then send the request.The text was updated successfully, but these errors were encountered: