<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z0000AIJFS6CQPOkta Classic EngineSingle Sign-OnAnswered2025-12-19T09:00:18.000Z2025-01-07T05:11:58.000Z2025-01-21T21:46:38.000Z

nvttm (nvttm) asked a question.

AWS OKTA SWA INTEGRATION NOT WORKING

Hello,

We attempted to integrate Okta AWS login using SWA, but it's not functioning correctly. The username value consistently overwrites the account ID input field.

The current Okta SWA plugin isn't performing as expected.

Could you suggest possible solutions or alternative ways to make this integration work through SWA only?


  • MatthewH.10249 (State of Iowa)

    Assuming you have the Okta Plugin installed on your browser it should be pretty basic setup. Are you perhaps having a password manager plugin (lastpass, etc) or is the browser storing your credentials and that is perhaps what causing the issue?

  • MatthewH.10249 (State of Iowa)

    Here is a post where someone had a similar issue a couple years ago but it does not seem like they found a fix. https://support.okta.com/help/s/question/0D54z00008KEE1aCAH/template-plugin-app-3-fields-failing-to-work?language=en_US

     

    I went ahead and created a "Template Plugin App 3 Fields" SWA on one of my preview Okta tenants and was able to use the IAM URL and CSS selector values you provided and it worked fine. My guess is that you may not have noticed that the ....org.signin.aws.amazon.com... URL redirects to a different URL and that is probably why things get blanked. I had to add "https://us-east-2.signin.aws.amazon.com/" as the value for the "Redirect URL" field in the Okta app settings. I also set "Extra field selector" with a value of "#account", "Extra field value" with a value of "ABC" (bogus value) and "Login button" with value of "#signin_button".

    Expand Post
This question is closed.
Loading
AWS OKTA SWA INTEGRATION NOT WORKING