Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a command to get an access token for an app #74

Open
mraible opened this issue Dec 23, 2020 · 2 comments
Open

Add a command to get an access token for an app #74

mraible opened this issue Dec 23, 2020 · 2 comments

Comments

@mraible
Copy link
Contributor

mraible commented Dec 23, 2020

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?!

okta token --app=XXX

Equally as good: generate one from the dashboard.

@mraible
Copy link
Contributor Author

mraible commented Mar 12, 2021

This would be nice so we don't have to tell people to use oidcdebugger.com.

@bdemers
Copy link
Contributor

bdemers commented Mar 24, 2021

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants