Challenge Handler not called in WPF

JoeHershman

Hi,

Am seeing some really odd behavior with Windows and authentication.  I have code that works fine in Xamarin forms on iOS.  Very simple, just setting up Authentication.  What I am seeing though is that in WPF (both Win standard and NET6) the challenge handler does not get called.  It just does not go into the method, and then I get an unauthorized error trying to open the item.  As I said, the same code works in Xamarin Forms, I can look at the AuthenticationManager and see a registered method for the challenge handler, but it does not enter the method.

Any thoughts on something additional needed in WPF.  I have gone through the samples and do not see anything being done that differs

Thanks - Joe

MatveiStefarov

Alright, thank your for this extra information!  I think I know what's going on.

Setting a global APIKey is meant to be an alternative to making users log into the app.  It is one of three ways to add an access token to app's network requests.  Mixing multiple token sources in one application can lead to problems.  What I think is happening in your case is -- having the API key set means that every request to arcgis.com already has an access token, which interferes with credential-challenge detection and can even prevent a TokenCredential from being used.

If your app will always require users to log in, then you probably don't need to use that API key.  See if removing the APIKey allows the ChallengeHandler and/or TokenCredential to work.

But if your app needs to have logging in optional -- e.g. by switching from API key to named-used authentication mid-flight -- that will be tricky.  That's not really a scenario we've tested so far, and I'd be curious to learn more about your use case.