LinkedIn
Twitter
I'm encountering an issue with a shared flow configuration involving a custom token generation response. Here's a breakdown of the problem:
Within the shared flow, I've implemented a custom response for token generation using an "Assign Message" policy to add a custom payload. Additionally, I've updated the GenerateAccessToken policy to enable GenerateResponse. While the response is indeed generated based on the custom payload, the request continues to target the endpoint, resulting in a 404 error indicating that the requested resource is not found. My expectation is to receive the custom payload response without the request proceeding to the target endpoint. Did i miss something? Raisefault not feasible for me 😞
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<SharedFlow name="default">
<Step>
<Name>OAuthV2-GenerateAccessToken</Name>
<Condition>(proxy.pathsuffix MatchesPath "/token") and (request.verb = "POST")</Condition>
</Step>
<Step>
<Name>AM-CustomResponse</Name>
<Condition>(proxy.pathsuffix MatchesPath "/token") and (request.verb = "POST")</Condition>
</Step>
<Step>
<Name>OAuthV2-VerifyAccessToken</Name>
<Condition>Not(proxy.pathsuffix MatchesPath "/token")</Condition>
</Step>
</SharedFlow>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<OAuthV2 continueOnError="false" enabled="true" name="OAuthV2-GenerateAccessToken">
<DisplayName>OAuthV2-GenerateAccessToken</DisplayName>
<ExpiresIn>1800000</ExpiresIn>
<SupportedGrantTypes>
<GrantType>client_credentials</GrantType>
</SupportedGrantTypes>
<Properties/>
<Attributes/>
<ExternalAuthorization>false</ExternalAuthorization>
<Operation>GenerateAccessToken</Operation>
<GenerateResponse enabled="false"/>
<Tokens/>
<RFCCompliantRequestResponse>true</RFCCompliantRequestResponse>
</OAuthV2><?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<AssignMessage continueOnError="false" enabled="true" name="AM-CustomResponse">
<DisplayName>AM-CustomResponse</DisplayName>
<Properties/>
<Set>
<Payload contentType="application/json">
{
"access_token": "{oauthv2accesstoken.OAuthV2-GenerateAccessToken.access_token}",
"expires": "{oauthv2accesstoken.OAuthV2-GenerateAccessToken.expires_in}",
"token_type": "{oauthv2accesstoken.OAuthV2-GenerateAccessToken.token_type}",
"status": "{oauthv2accesstoken.OAuthV2-GenerateAccessToken.refresh_token_status}"
}
</Payload>
</Set>
<IgnoreUnresolvedVariables>true</IgnoreUnresolvedVariables>
<AssignTo createNew="false" transport="http" type="request"/>
</AssignMessage>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ProxyEndpoint name="default">
<DefaultFaultRule name="all">
<AlwaysEnforce>true</AlwaysEnforce>
<Step>
<Name>FC-CustomException</Name>
</Step>
</DefaultFaultRule>
<PreFlow name="PreFlow">
<Request>
<Step>
<Name>FC-AuthFlow</Name>
</Step>
</Request>
<Response>
</Response>
</PreFlow>
<Flows/>
<PostFlow>
<Response>
<Step>
<Name>FC-CustomResponse</Name>
</Step>
</Response>
<Request/>
</PostFlow>
<HTTPProxyConnection>
<BasePath>/say-hello</BasePath>
</HTTPProxyConnection>
<RouteRule name="default">
<TargetEndpoint>default</TargetEndpoint>
</RouteRule>
</ProxyEndpoint>
