Nathan V

@korporationcl Keyman isn't built for Okta's AWS SSO module; it works with AWS IAM Federation which is why that URL doesn't match. They're different integrations and don't operate the same.

Reopening, I have support for AWS SSO in the works. It'll take a bit to get it parity with the main features that interact with Okta I think but I...

Hi @Hjusino. I don't have access to an environment today that uses RSA tokens unfortunately. I won't have a good way to test this.

If someone with access to an RSA token enabled environment can help test this out I'd appreciate getting any additional information. I believe this is supportable but I have no...

> @nathan-v I am currently using this in an RSA token enabled environment and would like to assist in the testing. Rad. I'll look into the Okta API side and...

Hi @SmithTM90 I've never seen that issue or case. Do you have an Okta setting that causes this?

If someone knows the setting required to cause this I can set it up in a test Okta to try and replicate. I'd love to be able to support this.

You can already do this today; an Okta account with multiple AWS entries should prompt you for which AWS account you want to use by default. Are you on an...

Ah, yeah! You want to refresh multiple at once. Something I've definitely considered and wanted to do before but I didn't have a strong need for it at my org....

Hi @wulftone. Have you tried using the tool without the appid sepecified? You'll get a list of AWS accounts to pick from that will have their friendly names (from Okta)...