I'm attempting to do a golang CLI proof-of-concept using Okta authentication. For example, I'm imagining a golang CLI client that accesses internal APIs using Okta access token (OIDC).
Also, from just studying the documentation here:
https://developer.okta.com/standards/OAuth/#basic-flows
It looks like 2. Native Application (Uses Authorization Code Grant Flow) would be the preferred flow and I'll compare that to the example.
Can you comment on if the approach of authenticating a CLI using Okta is viable, and if it is, confirm the preferred workflow?
Even better, if this approach is viable, providing an example in this repository would be a great help!
GowthamMS
commented
4 years ago
Thank you for this resource!
I'm attempting to do a golang CLI proof-of-concept using Okta authentication. For example, I'm imagining a golang CLI client that accesses internal APIs using Okta access token (OIDC).
I will study this example: https://github.com/segmentio/aws-okta
Also, from just studying the documentation here: https://developer.okta.com/standards/OAuth/#basic-flows It looks like
2. Native Application(Uses Authorization Code Grant Flow) would be the preferred flow and I'll compare that to the example.Can you comment on if the approach of authenticating a CLI using Okta is viable, and if it is, confirm the preferred workflow? Even better, if this approach is viable, providing an example in this repository would be a great help!