Skip to content
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

No device posture support #65

Open
monde opened this issue Feb 6, 2023 · 5 comments · May be fixed by #260
Open

No device posture support #65

monde opened this issue Feb 6, 2023 · 5 comments · May be fixed by #260
Labels
2.4.0 address in 2.4.0 release

Comments

@monde
Copy link
Collaborator

monde commented Feb 6, 2023

Need to update the README noting there is not device posture support in AWS Federation App / web SSO token at this time. Therefore it is not possible to achieve this in the okta-aws-cli.

Background notes:

“When device state is required in the authentication policy the processing on the AWS Application will fail to either the catch-all rule or alternative rule preventing aal3+ device trust requirements.”

"We have no means of collecting device posture on the token exchange call, so rules with that condition will not be hit"

"We are planning on greater investments to web_sso_token, expanding it to other use cases"

@joshgch
Copy link

joshgch commented Apr 21, 2023

Hey @monde , is this something that will be fixed in the future? This is causing an issue for us as we need both Web and CLI access to support ODT and Phish Resistant factors.

@stargonautone
Copy link

This is happening even without a Device State requirement (i.e. "AND Device state is" is set to "Any").

@stargonautone
Copy link

HTTP 400 errors caused by MFA challenge on our end were due to mismatched policy between Native OIDC app and AWS Account Federation SAML app. Issues were resolved by assigning the same (OIE) Authentication Policy to OIDC intermediary authZ and SAML authN apps.

@SpencerLN
Copy link

@monde, are there any plans and/or timeline to support device posture in okta-aws-cli in the future? Is there an internal ticket number we can reference with our account team to request prioritization?

@monde monde added the 2.4.0 address in 2.4.0 release label Jan 7, 2025
@monde
Copy link
Collaborator Author

monde commented Jan 7, 2025

To meet the https://github.com/okta/okta-aws-cli/labels/2.4.0 label the README will state "AWS Federation App / web SSO token does support device posture at this time. Therefore it is not possible to achieve this in the okta-aws-cli"

The note here: "We are planning on greater investments to web_sso_token, expanding it to other use cases" is from the team in Okta that owns the AWS Fed App, not the team that support okta-aws-cli. okta-aws-cli is a downstream interface from the Okta API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.4.0 address in 2.4.0 release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants