From API Portal / “Documentation” Tab, I'm trying the basic "Math" API (that was created by CA team support for testing), and I get "500 internal error" and "Assertion falsified" as policy result ; see attached screenshot.
Note that to try the "Math" API, I did the following : from API Portal / “Documentation” / “Math” / "Math/Add"
and I entered 2 figures then clicked and on “Try it “
Please advice how to progress, to solve this.
That indicates the /Math api could have problem, review the ssg log or audit event viewer should give you more details about the problem.
It's better to open a support ticket to review the policy and logs.
In audit, I can see
API Portal Integration Service [/portalman/*]
Message was not processed: Authentication Failed (402)
Not sure how to conclude.
Note : in the portal , the Math API appears in the "Documentation" Tab , but not in the "APIs & Plans" Tab
Thanks for your feeback and support.
I was wondering if the portal is configured properly to integrate with gateway, the document here,
4. Connect the API Portal to the Gateway - CA API Developer Portal - 3.5 - CA Technologies Documentation
talking about few "Sync" buttons on CMS, click those buttons and ensure all return HTTP 200.
If any problem of "Sync", that means portal cannot connect to gateway properly, you may have to check the integration steps again and see where is the problem.
When clicking on "Sync API Plans" as suggested, I get a failure message, as shown below. I understand that it means portal cannot connect to gateway properly and that integration steps need to be checked. (correct? ) These steps were done by CA team support guy, if I understand properly. I'm not sure if he can help. I will check and come back to you.
Yes, definitely something wrong with the integration. Please double check every step of the integration.
Have you tried using the Service Debugger?
OrYou can also add the Customize SOAP Fault Response assertion, edit the assertion and select Full Details, check Use SOAP Fault for all errors.
I tried Service Debugger or to add the assertion mentioned above , but I 'm not yet comfortable on how to use it and to conclude.
Let me know if any suggestions.
At this stage, I suggest a new CA support case be open to further troubleshoot.