About muthukkannan

muthukkannan · 09-19-2023

Hi,I see a similar a question raised in 2021, but that seem to be have been resolved, since it was a problem in variable referencing (referring to query param instead of form param). In the response it was stated scope has to be added during auth-cod...

muthukkannan · 09-13-2023

I was trying Dino's AWS Signing V4 - Java callout. In Target Request Pre-flow: 1. I was using AssignMessage to prepare request. AM-ConstructBackendRequest {private.id} Data.Read 12 {fromDate} {toDate} GET / lambdaRequest 2. In AWS Signing J...

muthukkannan · 09-26-2023

Hi Dino,Yes, the header values are getting set. It is just that in the trace it is not capturing (.xml) - so it is not displaying. I assumed trace was working properly. Thanks a lot.

muthukkannan · 09-20-2023

Hi Dino,Again, thanks a lot for the response. The usage is same (I had picked it from your devjam repository :-)). A bit strange. It is working now, the same revision. The scope values in API Product was the last change that I did; I had used space a...

muthukkannan · 09-19-2023

Hi Dino, Thanks for the response. Yes, I tried with 'request' in both AssignMessage and in Callout. And also have tried with 'message' as you have suggested. The result is same; in AssignMessage it sets the required headers and in Java callout it set...

My Stats

muthukkannan's Bio

Badges muthukkannan Earned

Recent Activity

GenerateAccessToken with Scope parameter for ClientCredentials is not reflected in the Token

AssignMessage SET request values missing in Target request if JavaCallout is in between

Re: AssignMessage SET request values missing in Target request if JavaCallout is in between

Re: GenerateAccessToken with Scope parameter for ClientCredentials is not reflected in the Token

Re: AssignMessage SET request values missing in Target request if JavaCallout is in between