Okta Advanced Server Access Error Resource Does Not Exist When Creating a New Team

Okta returns an error when creating a new team in Okta Advanced Server Access (ASA) if the changes made in the Okta Admin Console under the Sign On tab for the ASA application are not saved. Contact Okta Support to delete the team, then recreate it, ensuring the Okta configuration is saved before authenticating. When attempting to create a new team in ASA, Okta displays the following error after clicking Authenticate With Okta:

{"type": "resource_does_not_exist","code": 404,"message": "Resource does not exist"}

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Advanced Server Access (ASA) / ScaleFT

The error occurs when the changes made in the Okta Admin Console under the Sign On tab for the ASA application remain unsaved before attempting to authenticate.

How is the resource does not exist error resolved?

Contact Okta Support to delete the affected team, add the ASA application from the Okta Integration Network (OIN), and configure the application settings before authenticating.

1. Contact Okta Support to delete the team generating the error.
2. Once Okta Support deletes the team, log in to the Okta Admin Console and add a new Okta Advanced Server Access application from the Okta Integration Network (OIN).
3. Click the Assignments tab and assign the application to the appropriate administrators.
4. Click the Sign On tab, click Edit, and leave this page open.
5. Open a new browser tab, navigate to the Advanced Server Access homepage, and click Create New Team.
6. Enter the necessary information and click Get Started.
7. Keep this tab open to retrieve the Base URL and Audience Restriction values.
8. Copy the Base URL and Audience Restriction values from the ASA configuration tab and paste them into the Okta Admin Console tab opened in Step 4.
9. Right-click Identity Provider Metadata to open the link in a new tab, copy the URL, and paste it into the IdP Metadata URL field on the ASA configuration page.
10. Click Save in the Okta Admin Console first, then return to the ASA configuration tab and click Authenticate with Okta.

NOTE: It is critical to save the configuration in the Okta Admin Console before authenticating with Okta in the ASA tab.