If there is a value set in the API_METHOD parameter of the "Capture Identity of Requestor" assertion in any policies used by API Developer Portal, it can cause some of the following symptoms:
Note: The symptoms will specifically occur on the CA API Gateway, not the CA Developer Portal. However, this issue has (so far) only been seen when both the CA API Gateway and CA Developer Portal are integrated together, along with a value set for API_METHOD instead of kept at the default value of empty.
This behaviour is caused by any value set in the API_METHOD parameter of the "Capture Identity of Requestor" assertion in policies which are read by the CA API Developer Portal. By default, there is no value set for the API_METHOD parameter in the "Capture Identity of Requestor" assertion in policies read by the API Developer Portal, and the value should remain null.
If the API_METHOD has a value set rather than being left empty, the following steps should be performed to resolve the issue:
Prevention: Ensure that all values for any API_METHOD parameter in the "Capture Identity of Requestor" is left empty. Refrain from changing that parameter from the default empty value.