Solved! Go to Solution.
Hi,
it is possible to do it.
you can create fault rule example
<FaultRule name="OAuthValidationFailed"> <Step> <Name>OAuth-Validation-Failed</Name> </Step> <Condition>oauthV2.Verify-Acess-Token.failed == true</Condition> </FaultRule>
here OAuth-Validation-Failed is assign message policy
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <AssignMessage async="false" continueOnError="false" enabled="true" name="OAuth-Validation-Failed"> <DisplayName>OAuth Validation Failed</DisplayName> <Properties/> <Set> <Payload contentType="application/json">\{"error": \{"message":"{fault.name}", "detail":"Please provide valid access token in the Request Authorization header as - 'Bearer [access token]'"}} </Payload> <StatusCode>401</StatusCode> <ReasonPhrase>Unauthorized</ReasonPhrase> </Set> <IgnoreUnresolvedVariables>true</IgnoreUnresolvedVariables> <AssignTo createNew="false" transport="http" type="response"/> </AssignMessage>
Let me know it helps.
Please have a look at fault handling.
Hi,
it is possible to do it.
you can create fault rule example
<FaultRule name="OAuthValidationFailed"> <Step> <Name>OAuth-Validation-Failed</Name> </Step> <Condition>oauthV2.Verify-Acess-Token.failed == true</Condition> </FaultRule>
here OAuth-Validation-Failed is assign message policy
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <AssignMessage async="false" continueOnError="false" enabled="true" name="OAuth-Validation-Failed"> <DisplayName>OAuth Validation Failed</DisplayName> <Properties/> <Set> <Payload contentType="application/json">\{"error": \{"message":"{fault.name}", "detail":"Please provide valid access token in the Request Authorization header as - 'Bearer [access token]'"}} </Payload> <StatusCode>401</StatusCode> <ReasonPhrase>Unauthorized</ReasonPhrase> </Set> <IgnoreUnresolvedVariables>true</IgnoreUnresolvedVariables> <AssignTo createNew="false" transport="http" type="response"/> </AssignMessage>
Let me know it helps.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 | |
1 |