Okta ASA Group Push Failing with "User does not exist"
Last Updated:
Advanced Server Access
Okta Classic Engine
Okta Identity Engine
Overview
A group push from Okta to the Advanced Server Access (ASA) application fails when a user in the pushed group is in a deleted state in ASA. Activating the deleted user in ASA resolves the issue. The following error appears during the group push:
Not Found. Errors reported by remote server: User does not exist
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Advanced Server Access (ASA)
- Group Push
Cause
One or more users from the pushed group are in a deleted state in ASA. Okta generates the error because the request cannot find the mapped user in the target application.
Solution
How is the group push error resolved?
Identify the deleted user in ASA, change the user state to active, and push the group again from Okta.
- Identify the deleted user in ASA by comparing the ASA user list with the source user list from the Okta group.
- Select the Gear icon in ASA and change the state of the identified deleted user to Active.
- Push the group again from Okta.
