-
Notifications
You must be signed in to change notification settings - Fork 124
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 default account when no account name is provided to conjurctl
commands
#2082
Comments
+1 on calling the default account |
There was actually an internal email chain to make this official. @InbalZilberman: This is what we settled on, right? |
I love this... can we also expand this to any tooling that talks to Conjur that can automatically resolve the account name for an intsance? |
I maybe new to conjur, but, won't it create a potential security risk ? |
@dataplex that is the goal - all clients can also be updated to assume a default account name if none is provided. @amosmintzcyberark permissioning in Conjur remains the same, this just removes a manual configuration step that in the vast majority of cases is not required. |
Resolves #2082. Chose not to use `default_value` in `conjur-cli.rb` because the name can be provided by either a flag or argument, and having a default value set by GLI would make it difficult to ascertain which to use.
Resolves #2082. Chose not to use `default_value` in `conjur-cli.rb` because the name can be provided by either a flag or argument, and having a default value set by GLI would make it difficult to ascertain which to use.
If no account is passed to
conjurctl
commands have the account be set to a default value.Example:
conjurctl account create
would create an admin user for thedefault
account.The text was updated successfully, but these errors were encountered: