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
I've been thinking about this on and off for a bit.
Client credentials flows should be easy to do like this.
Browser-based flows get tricky because existing redirects would be wrong.
But for most of our blog posts (and i think typical usage of okta token) you would be testing a resource server, and a client creds flow might be all you need, so we might be able to do something like just okta token then:
look for a client with a given name (something like okta-cli-token) create it if it doesn't exist
do the client-creds dance
return a token
That might be a bit naive though, we should pick @aaronpk's brain about it too
We use the OIDC debugger in a lot of tutorials and often enable implicit flow to make things faster.
What if we could get an access token from the CLI?!
Equally as good: generate one from the dashboard.
The text was updated successfully, but these errors were encountered: