TokenSource parameter in not available in DurableHttpRequest constructor in Azure Durable function in Isolated mode

[vibhu12345]

The class DurableHTTPRequest does not support managed identity token source when using Azure Durable function in Isolated mode.
https://github.com/Azure/azure-functions-durable-extension/blob/dev/src/Worker.Extensions.DurableTask/HTTP/DurableHttpRequest.cs

But it is supported in in-process mode.
https://github.com/Azure/azure-functions-durable-extension/blob/4714ad1b0f4534a28d37a6871847543b8d43abc8/src/WebJobs.Extensions.DurableTask/DurableHttpRequest.cs

Please provide the solution for the same. If Isolated mode has lesser features than In-Process why is it recommended to upgrade it?

[cgillum]

Apologies for this. It seems that there's a functionality gap for the Durable HTTP feature between .NET in-proc and .NET Isolated. Things like the HTTP 202 polling and TokenSource integration have not yet been ported to .NET Isolated. This is something we plan to fix in the coming months. We can use this issue to track progress.

FYI @lilyjma

[dmunch]

Just been running into this as well - It's very unfortunate that this isn't clearly stated in the "Consuming HTTP Apis" documentation.

Anyone got an idea what's the best way to work around this until this is fixed? While I'm able to specify a custom authorization header, I'm not quite sure yet how to obtain the actual token. Having an activity to obtain the token seems wrong, as the token would be persisted.

Edit: I've been focused on missing the tokenSource for isolated functions, but re-reading this thread I realise that even HTTP 202 polling is not supported yet (Again, unfortunate that it's not clearly stated in the docs). My workaround will thus be implementing this myself in activities.