Okta Advanced Server Access Servers API Returns Empty List
Last Updated:
Okta Classic Engine
Okta Identity Engine
Advanced Server Access
Overview
When querying the Advanced Server Access (ASA) servers API, the response returns an empty list if the service user is not assigned to the project containing the servers. Assigning the service user to a group and adding that group to the correct project resolves the issue. The exact symptom occurs when sending a curl request to the server's API, which results in the following empty list response:
curl -Ss -i -X GET 'https://app.scaleft.com/v1/teams/<teamname>/servers' -H 'Authorization: Bearer <token>'
{
"list": []
}
{
"list": []
}
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Advanced Server Access (ASA)
- API
Cause
The ASA service user lacks assignment to the project where the servers reside.
Solution
How is the empty server list issue resolved?
Assign the ASA service user to a group, then add that group to the project containing the servers by completing the following steps.
- Assign the ASA service user to an ASA group.
- Add the group to the project where the servers reside.
