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

Remove Okta? #10

Open
0xdabbad00 opened this issue Mar 16, 2022 · 0 comments
Open

Remove Okta? #10

0xdabbad00 opened this issue Mar 16, 2022 · 0 comments

Comments

@0xdabbad00
Copy link
Contributor

I received the following guidance from Okta:

we have an existing workaround solution that allows customers to disable the use of IMDSv1 by enabling IMDSv2 only. Please see our product documentation for more details on this workaround here: https://help.okta.com/asa/en-us/Content/Topics/Adv_Server_Access/docs/features-by-platform.htm.

The work-around here is to manually configure the information into a config file on the EC2 so that the agent doesn't need to reach out to the metadata server. This is not an acceptable workaround to me as it moves work from Okta to the customer unnecessarily as the work for Okta should be much simpler than this workaround.

As such, I will not be removing Okta until the Okta ASA Agent supports IMDSv2.

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

No branches or pull requests

1 participant