You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DownstreamWebApi.CallWebApiForUserAsync implementation currently merges options from initial configuration and calledApiOptionsOverride by cloning the initial options and then invoking the override action:
The problem is that Clone does not include the CustomizeHttpRequestMessage property on DownstreamWebApiOptions, which means that it is just null and you thereby lose the original configuration for that property.
If users do not want to use the strongly typed extensions because they need more control, they then cannot use the CustomizeHttpRequestMessage setting at all unfortunately.
Microsoft.Identity.Web Library
Microsoft.Identity.Web
Microsoft.Identity.Web version
1.25.5
Web app
Sign-in users and call web APIs
Web API
Protected web APIs call downstream web APIs
Token cache serialization
In-memory caches
Description
DownstreamWebApi.CallWebApiForUserAsync
implementation currently merges options from initial configuration andcalledApiOptionsOverride
by cloning the initial options and then invoking the override action:The problem is that Clone does not include the
CustomizeHttpRequestMessage
property onDownstreamWebApiOptions
, which means that it is just null and you thereby lose the original configuration for that property.If users do not want to use the strongly typed extensions because they need more control, they then cannot use the
CustomizeHttpRequestMessage
setting at all unfortunately.Reproduction steps
Error message
No response
Id Web logs
No response
Relevant code snippets
Regression
No response
Expected behavior
Expected the
CustomizeHttpRequestMessage
setting to behave as all other settings and not be cleared.The text was updated successfully, but these errors were encountered: