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
The plugin allows setting multi-factor authentication. I am using an enterprise account without the IAM privileges. I login via OKTA and am presented with the following access details after login:
Currently I can update the access key id and secret access key fields on 1password:
However, I am unable to provide the AWS_SESSION_TOKEN value. Therefore, to be able to login, I have to expose the password via variable definition in the terminal before calling any aws command:
export AWS_SESSION_TOKEN=""
aws s3 ls
Would it be possible to be able to set such variable in the relevant 1password item? Or how would do you recommend approaching this?
Relevant log output
If I don't provide the AWS_SESSION_TOKEN inline, I get the following error:An error occurred (InvalidAccessKeyId) when calling the ListBuckets operation: The AWS Access Key Id you provided does not exist in our records.
The text was updated successfully, but these errors were encountered:
cellulosa
added
the
op-cli
Functionality to be implemented in 1Password CLI. Needs to be done by 1Password Developers.
label
May 1, 2024
op CLI version
2.28.0
Goal or desired behavior
The plugin allows setting multi-factor authentication. I am using an enterprise account without the IAM privileges. I login via OKTA and am presented with the following access details after login:
Current behavior
Currently I can update the
access key id
andsecret access key
fields on 1password:However, I am unable to provide the
AWS_SESSION_TOKEN
value. Therefore, to be able to login, I have to expose the password via variable definition in the terminal before calling anyaws
command:Would it be possible to be able to set such variable in the relevant 1password item? Or how would do you recommend approaching this?
Relevant log output
The text was updated successfully, but these errors were encountered: