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 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.
The text was updated successfully, but these errors were encountered:
I received the following guidance from Okta:
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.
The text was updated successfully, but these errors were encountered: