With our recent cloud release we replaced the names of some apigee generated faults (fault.name) with the new ones to achieve some standardization. This might have affected some API flows which were explicitly doing a string match for a particular fault.name string. We have rolled back all the fault.names to the older values except one.
If you are using a check on the fault name "invalid_client" in any of your flows as a condition, then we suggest that you add an extra condition to match the new value so that it does not affect your API calls.
Literally - if you have a condition like (fault.name = "invalid_client") PLEASE change that to
- (fault.name = "invalid_client") OR (fault.name = "InvalidClientIdentifier") so that you have that extra match and the API calls would proceed as expected.
We typically noitfy and also document these changes along with our release notes. Looks like our release preceded the other aspects. We sincerely apologize for the inconvenience caused, if you were affected, due to this change and lack of the documentation at the time of releasing this feature.
Contributors
41 People are following this .
