Unexpected behaviour in Get User ACL

 

You’re now watching this thread. If you’ve opted in to email or web notifications, you’ll be notified when there’s activity. Click again to stop watching or visit your profile to manage watched threads and notifications.

 

You’ve stopped watching this thread and will no longer receive emails or web notifications when there’s activity. Click again to start watching.

  For some of the ASA account Get User ACL api is working fine without X-AP-Context in the header. But for some of the ASA account we are getting 403 response code. As per API details X-AP-Context is not a mandatory field. If we provide X-AP-Context for failed ASA account it works fine.