Travis Walker

Resolved in [4.15](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/releases/tag/4.15.0)

So I am able to reproduce this and it Looks like there are some additional configurations that are needed in order for us ot access the data in this header....

If MSAL is not updated and this started happening suddenly, it usually points to an Entra Id service endpoint issue. @ashok672 have you seen this in WAM before?

Hi @d-philipson, Are you able to provide verbose logs? https://learn.microsoft.com/en-us/entra/msal/dotnet/advanced/exceptions/msal-logging

Might be related to our deprecations here but not 100% sure. [4.58.0](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/releases/tag/4.58.0) @bgavrilMS Dont think we did testing with net 8 yet https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/issues/3985

> Thanks @trwalke , given that CIAM non-CUD works, I'm marking this as a P3. > > For Id.Web to support other OIDC authorities, this needs to be fixed. This...

> @trwalke - the current CIAM daemon sample advises to use the Authority as > >  > > https://github.com/Azure-Samples/ms-identity-ciam-dotnet-tutorial/blob/main/2-Authorization/3-call-own-api-dotnet-core-daemon/ToDoListClient/appsettings.json > > I believe this works (and there are some...

Moving to next quarter

> They can't, there are tests that are disabled on OneBranch related to public client. Not expecting to fix them. What other steps are you thinking of? @bgavrilMS we can...

> As part of this we should also add a clear code snippet in our docs on how to do this: > > > Correct pattern is: > > Extract...