Apigee Oauth Generate Access Token Does Raise Faults

Google Cloud Apigee
1

Hi I am facing issue similar to this post

Need information on how to solve this

2

Hello @vs098,

Are you able to describe in more detail what issues you are facing?

If you are worried about lack of access to the noted screencast (given the link returns a 404) you can see the referenced video here: https://www.youtube.com/watch?v=Cr3hO5jT9cI

Best
Matt

1 Like
3

Yes, and here is the updated link to the article

4

Hey,

Hope you’re keeping well.

In Apigee, when handling invalid_client or other OAuth errors, the key is to match the exact fault name and scope in your FaultRule conditions. Make sure your Condition in the FaultRule matches the fault.name value emitted by the OAuth policy, for example:

<FaultRule name="InvalidClientFault">
    <Condition>(fault.name = "invalid_client")</Condition>
    <Step>
        <Name>RaiseFault</Name>
    </Step>
</FaultRule>

Also ensure the FaultRule is placed at the correct level in the API proxy XML—either in the ProxyEndpoint or TargetEndpoint depending on where the OAuth policy runs. You can inspect the exact fault.name value by enabling Trace in Apigee Edge and reproducing the error to confirm the match.

Thanks and regards,
Taz