Hi,
We have a web application that uses the CUCM's AXL and Serviceability APIs.
This app worked well in production and development environments until our last patch update to the CM in both environments.
Current CM version is: 11.5.1.15900-18.
Previous CM version is: 11.5.1.12900-21.
After the patch update, calls to AXL API only, returns with a 403 forbidden HTTP status code.
A sample AXL request is attached. Calls to the RisPort70 endpoint returns with a 200 status code as expected.
As noticed, here are some requests and their resposnes's status code:
GET ../axl returns with 200 --The only request that returns with a 200 status code.
POST ../axl/listPhone returns with 403 (with or without a basic authentication header)
POST ../axl/getPhone returns with 403 (with or without a basic authentication header)
Actions that were taken in order to try solve the issue:
- Giving full permissions in the AXL API scope to the application user: 'Standard AXL API Access' role. Also tried to add/replace with ‘Standard AXL API Users’ and ‘Standard AXL Read Only API Access’ roles
- Use an Admin user
- Changing Debug Trace Level to 'Debug' and collecting CM logs- especially AXL logs as described here.
We found only informational entries that indicates of an HTTP 403 status code responses, with no additional relevant data for this issue
- Checking for AXL scheme changes. As in documentation- "Maintenance releases never include new AXL schemas (for example, n.n.N)."
Any ideas for what can cause this issue?
Thanks in advance,
Leeor
