Hi Team,
I'm implementing an asynchronous remote backend call using Invoke Remote. To manage these calls, I'm pushing them to a queue and have defined a consumer that handles the actual API call to the backend.
While the Forge Invocation Token (FTI) is successfully attached and includes details like Cloud Id and App Id, I’ve noticed that the Principal (or Account Id) is missing from the token payload. This information is crucial for identifying the user initiating the request on my backend.
It appears the user context is not being picked up properly when processing the event from the queue. Could you please help clarify how to ensure the user context, specifically the Principal, is retained and included in the FTI when making remote calls from a queue consumer?
Thank you for your support.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.