Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
- What I did
Fixes #162, or at least makes it less painful.
A little bit of background...
Upon first login using the
2fa-login
endpoint, a token is returned which gives the user full access to all Hub APIs. When refreshing the token, the resulting token has reduced permissions, and so some APIs that initially worked with the first token will now fail. Until the Hub API is modified to allow refreshed tokens to have the same access as the first token, we need to do another prompt of the user's OTP to get another token which gives the tool full access to the Hub APIs.- How I did it
- How to verify it
Below is output from some commands I ran and the date when they were run to show it working.
Here is the first run with a token that is expired.
Then we run it again within the TTL of the token (30 minutes) and no reprompting of the OTP is required.
One last run shows that the token has expired, again, and we are correctly prompted to provide the OTP for 2FA authentication
- Description for the changelog
- A picture of a cute animal (not mandatory)