REST calls have empty Bearer token in the newest version (0.4.21)

[pareszka]

I upgraded Dataverse.Client and some of my tests started to fail. Retrieving records still work, as it's going through SOAP, but creating a new one fails. The exceptions is just:
JsonReaderException: Error reading JObject from JsonReader. Path '', line 0, position 0.

I checked with Fiddler what exactly is going on. I called CreateAsync for a contact, I can see successful calls for RetrieveCurrentOrganizaton, WhoAmI and for retrieving EntityMetadata, but then there is a POST to /api/data/v9.2/contacts, which is getting status 401.
I checked requests headers and this is how Authorization header looks like:

I compared the call from my app with older version of Dataverse.Client (0.4.19), and it looks normally there:

I also noticed that Cookies section is empty for new version, when for old version it looks like that:

[MattB-msft]

Could you give us a bit more info on what your code does for authentication and use case?

Also is this happening immediately? Or after some time ?

Thanks

[Garbageous]

We are getting this same error.

This seems to be happening to us when we try to update/delete SalesOrder.

We used this guide with our ops to set up the auth: https://docs.microsoft.com/en-us/powerapps/developer/data-platform/use-single-tenant-server-server-authentication

We use this to retrieve the token

This is the the code where the call fails (on savechanges):

[MattB-msft]

@Rtalos , thanks for adding info..

I am seeing the following:
Your managing the token on your own, passing in a handler to the constructor, whenever the client needs the token its going to call "GetToken", which I assume you have code to manage that. ( You didn't include that, just GetAzureToken which does not seem to be called anywhere ) . I am going to guess your using the memory cache to be your token cache.

Your then creating a clone and passing that to RemoveSalesOrders via DI,
In there, your setting up a Service Context, and using a linq operation to execute an update, ( in this case a delete ), and the token is not being appended to the WebAPI calls, it IS there on the OrganziationService calls.

is that accurate?

what version of .net are you using and what host platform? ( windows / non windows?)
Also can you confirm that your code "GetToken" is returning tokens all the time?

[Garbageous]

@MattB-msft , thank you for the response!

Yes, your assumptions are correct (sorry I missed adding the in-memory method), there is an in-memory cache between GetAzureToken method and GetToken inside the token provider function. It looks like this, I have also tried bypassing this but it is still the same error:

To answer your question.

What version of .net are you using and what host platform? ( windows / non windows?)

We use netcore 3.1 and I am currently developing this project on my local computer on Windows 10 OS.

Also can you confirm that your code "GetToken" is returning tokens all the time?

From what I can see, yes. I did also bypass the in-memory logic and it still produces the same error.

To add a bit more information. I did some more testing today and the first thing I wanted to try was to go back to the 0.4.20 version. I only downgraded the Microsoft.PowerPlatform.Dataverse.Client package, like so:

This seems to work. Looking through fiddler and this is what I see:

I then went back to 0.4.21:

And again it's producing the error. I have tried multiple different entities and they all give 401:

What is interesting is that it seems to only be when saving changes. If I do a simple select it still works and it is the correct product that is being returned:

[MattB-msft]

Ok, that helps us lock this down in conjunction with a set of other, nonvisable changes, that occurred in the 4.21 release..
We are looking for the issue now..
thanks!

[MattB-msft]

@Rtalos Your issue should now be fixed, Can you retest please with the 0.5.2 package.,
@pareszka Could you please retest now with 0.5.2 package please.

[Garbageous]

@MattB-msft

Sadly the issue seems to persist for us. Source code is unchanged from last post.

ServiceClient LastError:

[MattB-msft]

@Rtalos can you share a 'working' repro of your issue with us? As well as a verbose log from your client showing the failure?

If you can create a temp private repro on git, you can share it directly with me for us to look at.

We thought we had your issue identified and fixed but we're not 100% sure which is why we didn't close the issue.

Thanks

[Garbageous]

@MattB-msft ok, Ill see what I can do with the repro.

For now I found this aswell in same controller switching between 0.4.20 and 0.5.2 on the injected ServiceClient. Don't know if it helps.

[Garbageous]

@MattB-msft

I managed to get a repro working, this produces the exact same behaviour as our main app.

https://github.com/Rtalos/ServiceClientReproIssue162

I don't know how useful this will be because I am limited in what I can share (even privately). If you really need the information below to be able to solve this issue I can try to talk to management again and see what we can do:

• I am not allowed to disclose
  • Dynamics URL
  • Azure Tenant ID
  • Azure Client Secret
  • Azure Client ID

[MattB-msft]

@Rtalos Prefect, we will dig in and see what is going on, thanks !

[MattB-msft]

@Rtalos Confirmed bug.. we are working though understanding why this is happening in this case.