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 want to use oktaauth with more than one app (e.g. multiple AWS accounts)
I have an app with multiple users (e.g. an AWS account for infrastructure training), and I want to make it easier for them to use oktaauth.
Currently I need to either type the arguments on the command-line every time I run the tool (yeah, command history helps), or else write a separate wrapper shell script for each app.
I'd prefer an easier way to set the parameters so I can re-use them. Two ways that would be handy:
A configuration file, probably directory-based. For example, if I have a file named .oktaauth in my current directory, parent of my current directory, or up the tree to my home directory, then it uses that.
If I set environment variables, e.g. OKTA_USERNAME, OKTA_APP_ID, OKTA_SERVER, then oktaauth uses those.
My ideal would be for oktaauth to support both. So I think the conventional precedence would be: 1) command-line arguments 2) environment variable 3) configuration file. I guess it could also take a command-line argument that points to a particular file, and that would probably(?) come between 1 and 2?
The text was updated successfully, but these errors were encountered:
Howdy!
Two use cases for this request:
Currently I need to either type the arguments on the command-line every time I run the tool (yeah, command history helps), or else write a separate wrapper shell script for each app.
I'd prefer an easier way to set the parameters so I can re-use them. Two ways that would be handy:
.oktaauth
in my current directory, parent of my current directory, or up the tree to my home directory, then it uses that.My ideal would be for oktaauth to support both. So I think the conventional precedence would be: 1) command-line arguments 2) environment variable 3) configuration file. I guess it could also take a command-line argument that points to a particular file, and that would probably(?) come between 1 and 2?
The text was updated successfully, but these errors were encountered: