I have been following your thread and I love it!
We agree with you and Ben: any page that requires authentication should redirect you back to that page following successfully authentication. We’ll get that taken care of soon.
Possible for sure. We’'ll consider adding it - thanks for the suggestion.
That is definitely not how it’s supposed to work - it should be instant. However, your report prompted us to look and we’ve discovered an issue that is causing up to a one-minute delay before a new personal access token becomes active. We’ll put that on the bug list and get a fix into a future API release.
Ah, now we’re getting to the crux of your issue. What you’re describing is exactly why Oauth2 exists - it allows you to generate a token automatically, seamlessly. It’s the way our third-party integrations work (Amazon Alexa, Google Home, Samsung Smartthings, IFTTT) . It is by far a better solution for an app like yours compared to using personal access token. As @peter mentioned, it’s a little more work but it will provide a MUCH better user experience.
In addition to the Oauth2 documentation, you may also want to give this Update to API documentation announcement a read, if you haven’t already.
And thanks to you for reaching out and for this very cool application of the Tempest System! We are happy to support these kind of projects!