- Ensure evaluation of CLI flag for profile is in the same order as the other flags #124
- Retry cached access token if it isn't expired by but receives API error #127
- Friendly IdP and Role labels don't also print out ARN value (less text clutter in the UI)
- Friendly Role menu labels for long ARN values can be set in
$HOME/.okta/okta.yaml
- Remove okta-only domain check #103, thanks @duytiennguyen-okta!
- Cache Okta API access token #100, thanks @monde!
- Bringing in @tim-fitzgerald's PR #56
x_security_token_expires
value #56 #99, thanks @tim-fitzgerald! - Prepend OKTA_AWSCLI_ on ENV VARs #98, thanks @monde!
- Config for IdP menu #97, thanks @monde!
- Send browser command stdout to stderr #93, thanks @daniel-sampliner!
- Refactor config #90, thanks @duytiennguyen-okta!
- Update aws-cli with best practices #88, thanks @duytiennguyen-okta!
--expiry-aws-variables
CLI flag forx_security_token_expires
support in AWS creds file--cache-access-token
CLI flag to cache the access token associated device authorization to preempt needing to open the browser frequently- Friendly IdP menu labels for long ARN values can be set in
$HOME/.okta/okta.yaml
The following ENV VARs have been renamed
old value | new value |
---|---|
AWS_IAM_IDP |
OKTA_AWSCLI_IAM_IDP |
AWS_IAM_ROLE |
OKTA_AWSCLI_IAM_ROLE |
AWS_SESSION_DURATION |
OKTA_AWSCLI_SESSION_DURATION |
FORMAT |
OKTA_AWSCLI_FORMAT |
PROFILE |
OKTA_AWSCLI_PROFILE |
QR_CODE |
OKTA_AWSCLI_QR_CODE |
OPEN_BROWSER |
OKTA_AWSCLI_OPEN_BROWSER |
AWS_CREDENTIALS |
OKTA_AWSCLI_AWS_CREDENTIALS |
WRITE_AWS_CREDENTIALS |
OKTA_AWSCLI_WRITE_AWS_CREDENTIALS |
LEGACY_AWS_VARIABLES |
OKTA_AWSCLI_LEGACY_AWS_VARIABLES |
DEBUG_API_CALLS |
OKTA_AWSCLI_DEBUG_API_CALLS |
Multiple AWS environments requires extra configuration for non-admin users. Follow these steps to support non-admin users.
-
Create a custom admin role with the only permission being "View application and their details", and a resource set constrained to "All AWS Account Federation apps".
-
Create a group that will contain the AWS custom admin role users.
-
Add a rule on the admin console authentication policy that denies access if the use is a member of the group from step 2.
-
Assign non-admin users this custom role in step 1 and assign them to the group in step 2.
The "Admin" button will be visible on the Okta dashboard of non-admin users but they will receive a 403 if they attempt to open the Admin UI.
It is on our feature backlog to get support into the Okta API to allow the multiple AWS Fed apps feature into okta-aws-cli without needing this work around using a custom admin role.
- Remove an extra colon in usage text #76, thanks @ZhongRuoyu!
- Deal with deprecated/obsolete/unsupported
aws_security_token
variable #79, thanks @monde! - added proxy support to http client #80, thanks @SaltyPeaches!
- Try to help the operator if they are using a URL format value for org #82, thanks @monde!
- Pre-flight check if org is Classic or OIE #84, thanks @monde!
- Promote AWS_REGION from .env if it exists for proper AWS API behavior #85, thanks @monde!
- Emit tar.gz and zip archives upon release #87, thanks @monde!
- Fix "SETX commands emitted on Windows have incorrect syntax" #78, thanks @laura-rodriguez!
- Correctly set session duration from AWS_SESSION_DURATION env var #81, thanks @monde!
- Update golang/text dependency #71, thanks @laura-rodriquez!
- update dependencies #73, thanks @duytiennguyen-okta!
In the v1.0.0 release ENV VARs specific to okta-aws-cli will be prefixed with
OKTA_
in 12factor format.
old value | new value |
---|---|
AWS_IAM_IDP |
OKTA_AWS_IAM_IDP |
AWS_IAM_ROLE |
OKTA_AWS_IAM_ROLE |
AWS_SESSION_DURATION |
OKTA_AWS_SESSION_DURATION |
FORMAT |
OKTA_FORMAT |
PROFILE |
OKTA_PROFILE |
QR_CODE |
OKTA_QR_CODE |
OPEN_BROWSER |
OKTA_OPEN_BROWSER |
AWS_CREDENTIALS |
OKTA_AWS_CREDENTIALS |
WRITE_AWS_CREDENTIALS |
OKTA_WRITE_AWS_CREDENTIALS |
LEGACY_AWS_VARIABLES |
OKTA_LEGACY_AWS_VARIABLES |
DEBUG_API_CALLS |
OKTA_DEBUG_API_CALLS |
setx
output when in Windows environment #49, thanks @monde!--write-aws-credentials
implies output formataws-credentials
#40, thanks @monde!- Verbose HTTP API call/response logging with
--debug-api-calls
flag #43, thanks @monde! - Return underlying Error if present in fetchWebSSO() #47, thanks @emanor-okta!
- Fix setting/getting IDP ARN value when Role Value Pattern is used on AWS Federation App #51, thanks @monde!
- Accept
OPEN_BROWSER
,WRITE_AWS_CREDENTALS
env vars #50, thanks @monde!
First GA release
- Auto pop system web browser to device authorization form when
--open-browser
CLI flag is present - PR #21 - Full multiple AWS Federation Applications support - see README - Multiple AWS environments - #28
- Thanks @monde!
- Write/update (instead of append) AWS Credentials file when
--write-aws-credentials
CLI flag is present - PR #30
- Print response body with error message when API error occurs #22
- Thanks @ctennis!
- Don't render ncurses select menu for IdP or Role when there is only one item to choose from #25
- Thanks @ctennis!
- Document policy recommendation for AWS Fed App and OIDC Native App
- Document need for
AWS_REGION
env variable if AWS IdP is in a non-commercial AWS region - Auto-correct org domain when it is in admin form -
ORGNAME-admin.okta.com
toORGNAME.okta.com
- Illustrate
make tools
is used to install the tools the Makefile makes use of - Notorizing OSX x86_64 and arm64 binaries
- Correctly write creds file when
AWS_CREDENTIALS
env var is set AWS_PROFILE
is unnecessary in env var output
- Configurable AWS Session TTL
--session-duration [value]
#14. Thanks, @tim-fitzgerald! - Documentation improvements #13, #12 . Thanks, @BryanStenson-okta!
MVP release
MVP release
Release testing
Initial implementation