UWP authentication sometimes crashes #1098

tipa · 2019-04-19T10:35:13Z

Which Version of MSAL are you using ?
MSAL 3.0.5-preview

Platform
UWP

In my UWP app, I only had internetClient capability enabled and it works ok for most users. However, some of my users get an error like

{Microsoft.Identity.Client.MsalException: WAB authentication failed ---> System.IO.FileNotFoundException: The specified protocol is unknown. (Exception from HRESULT: 0x800C000D) at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) ...(TRUNCATION)... --- End of stack trace from previous location where exception was thrown --- at UserDetailsClient.MainPage.d__2.MoveNext() ErrorCode: authentication_ui_failed}

Therefore I investigated about what could be the problem and found out it could be related to the app capabilites.
Could you please clarify regarding the capabilites needed for UWP.

Here, @jennyf19 states these 4 capabilities are needed:

  <Capabilities>
    <Capability Name="internetClient" />
    <Capability Name="privateNetworkClientServer" />
    <uap:Capability Name="enterpriseAuthentication" />
    <uap:Capability Name="userAccountInformation" />
  </Capabilities>

However, in this example, these 4 capabilities are listed (sharedUserCertificates instead of userAccountInformation):

  <Capabilities>
    <Capability Name="internetClient" />
    <Capability Name="privateNetworkClientServer" />
    <uap:Capability Name="enterpriseAuthentication" />
    <uap:Capability Name="sharedUserCertificates" />
  </Capabilities>

Then again, in this example, only this capability is listed:

  <Capabilities>
    <Capability Name="internetClient" />
  </Capabilities>

Two of the above capabilites, sharedUserCertificates & enterpriseAuthentication, are restricted capabilites and I would only want to include them if they are indeed needed.

All very confusing. Could you maybe clarify here and in the docs?

The text was updated successfully, but these errors were encountered:

tipa · 2019-09-06T09:14:48Z

Still hitting this issue, just received a report with this stack trace. Any updates to this?

MSAL.UAP.4.3.1.0.MsalException: 
        ErrorCode: authentication_ui_failed 
Microsoft.Identity.Client.MsalException: WAB authentication failed ---> System.Exception: Der Prozess wurde unerwartet beendet. (Exception from HRESULT: 0x8007042B)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21 
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70 
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38 
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17 
   at Microsoft.Identity.Client.Platforms.uap.WebUI.<>c__DisplayClass7_0.<<AcquireAuthorizationAsync>b__0>d.MoveNext() + 0x1c8
--- End of stack trace from previous location where exception was thrown --- 
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21 
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70 
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38 
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17 
   at Microsoft.Identity.Client.Platforms.uap.DispatcherTaskExtensions.<>c__DisplayClass0_0`1.<<RunTaskAsync>b__0>d.MoveNext() + 0x133
--- End of stack trace from previous location where exception was thrown --- 
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21 
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x

bgavrilMS · 2019-09-09T12:31:32Z

Hi @tipa - any chance you could list the capabilities for you app?

Also, is the stack trace identical to the one posted by the OP? Google translates is as "The process ended unexpectedly" - this may be a bug in WAB / calling WAB.

tipa · 2019-09-09T13:45:15Z

I am currently using these capabilites:

  <Capabilities>
    <Capability Name="internetClient" />
    <uap:Capability Name="appointments" />
    <uap:Capability Name="userAccountInformation"/>
    <Capability Name="privateNetworkClientServer"/>
    <DeviceCapability Name="location" />
    <DeviceCapability Name="proximity" />
  </Capabilities>

I am actually not sure any more where I took the stack trace from in my first post, but I checked my mails for previous stack traces and found these:

Microsoft.Identity.Client.MsalException: WAB authentication failed ---> System.IO.FileNotFoundException: The system cannot locate the resource specified. (Exception from HRESULT: 0x800C0005)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21 
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70 
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38 
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17 
   at Microsoft.Identity.Client.Platforms.uap.WebUI.<>c__DisplayClass7_0.<<AcquireAuthorizationAsync>b__0>d.MoveNext() + 0x1c8
--- End of stack trace from previous location where exception was thrown --- 
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21 
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70 
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38 
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17 
   at Microsoft.Identity.Client.Platforms.uap.DispatcherTaskExtensions.<>c__DisplayClass0_0`1.<<RunTaskAsync>b__0>d.MoveNext() + 0x133
--- End of stack trace from previous location where exception was thrown --- 
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21 
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70 
   at System.Runtime.CompilerServices.Ta

Microsoft.Identity.Client.MsalException: WAB authentication failed ---> System.Exception: The process terminated unexpectedly. (Exception from HRESULT: 0x8007042B)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Microsoft.Identity.Client.Platforms.uap.WebUI.<>c__DisplayClass7_0.<<AcquireAuthorizationAsync>b__0>d.MoveNext() + 0x1c8
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Microsoft.Identity.Client.Platforms.uap.DispatcherTaskExtensions.<>c__DisplayClass0_0`1.<<RunTaskAsync>b__0>d.MoveNext() + 0x133
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServi

Microsoft.Identity.Client.MsalException: WAB authentication failed ---> System.IO.FileNotFoundException: Das System kann die angegebene Datei nicht finden. (Exception from HRESULT: 0x80070002)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Microsoft.Identity.Client.Platforms.uap.WebUI.<>c__DisplayClass7_0.<<AcquireAuthorizationAsync>b__0>d.MoveNext() + 0x1c8--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Microsoft.Identity.Client.Platforms.uap.DispatcherTaskExtensions.<>c__DisplayClass0_0`1.<<RunTaskAsync>b__0>d.MoveNext() + 0x133--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Microsoft.Identity.Client.Platforms.uap.DispatcherTaskExtensions.<RunTaskAsync>d__0`1.MoveNext() + 0x261--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Microsoft.Identity.Client.Platforms.uap.WebUI.<AcquireAuthorizationAsync>d__7.MoveNext() + 0x1f4   --- End of inner exception stack trace ---
   at Microsoft.Identity.Client.Platforms.uap.WebUI.<AcquireAuthorizationAsync>d__7.MoveNext() + 0x2a6--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Microsoft.Identity.Client.Internal.Requests.InteractiveRequest.<AcquireAuthorizationAsync>d__10.MoveNext() + 0x1a2--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Microsoft.Identity.Client.Internal.Requests.InteractiveRequest.<ExecuteAsync>d__9.MoveNext() + 0x18d--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Microsoft.Identity.Client.Internal.Requests.RequestBase.<RunAsync>d__14.MoveNext() + 0x3c8--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Microsoft.Identity.Client.ApiConfig.Executors.PublicClientExecutor.<ExecuteAsync>d__2.MoveNext() + 0x194--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17 ```

tipa · 2019-09-17T15:41:32Z

Any updates on this? Is the capability "internetClient" the only one that's needed? Even when logging in to a OneDrive for Business Account?

bgavrilMS · 2019-09-17T16:19:15Z

I do believe that InternetClient is the only one needed. the other 3 "enterprisey" ones are used in Integrated Windows Authentication (i.e. Kerberos) to figure out the currently logged in user. MSAL does not have any special code paths related to resources / scopes - there is nothing different in accessing OneDrive versus accessing Graph.

bgavrilMS · 2019-09-17T16:20:29Z

For the reports you keep getting, can you confirm if the problem is transient or not? Does reopening the app allow users to re-login?

tipa · 2019-09-18T07:32:26Z

For the reports you keep getting, can you confirm if the problem is transient or not? Does reopening the app allow users to re-login?

I asked my users that encountered the issue and one responded that he kept getting the error permanently, even after restart of the app and PC

bgavrilMS · 2019-09-18T10:51:49Z

Will treat this as a bug. MSAL delegates the auth part of the WAB component (Windows Authentication Broker).

jmprieur · 2019-09-18T14:39:42Z

@tipa : I think you read the readme for this sample: https://github.com/azure-samples/active-directory-xamarin-native-v2#UWP-specific-considerations, but checking in case?

tipa · 2019-09-18T16:20:24Z

No I'm not using the UseCorporateNework property in my app.
Regarding the WAB crashes: I don't think this is necessarily a MSAL specific issue as the same problem also happens when these users try to login via Google or Dropbox (for which I use WebAuthenticationBroker directly). But it would be great to understand why this happens and if there's anything I or the user can do to resolve it.

bgavrilMS · 2019-09-26T10:32:10Z

Hi @tipa

I've followed this up with the folks who own this component. Firstly, they confirmed that the capabilities used are as you described

Second, the need more information around the error, i.e. WAB logs. They have pointed at: https://docs.microsoft.com/en-us/windows/win32/secauthn/web-authentication-problems

jmprieur · 2019-09-26T18:11:32Z

Provide an exception that says that it looks the file is corrupted (apparently that happens to DPAPI files?), and provide the API so that the app deletes it if it wants.
MsalCacheCorruptedException

Retry()
Delete()

or

just delete the file.

Make sure we have enough logging, and also let the app dev know through an exception. The exception should have all the information about the fact that the file was deleted and recreated because corrupted (#supportablity)

tipa · 2019-09-27T15:24:59Z

Thanks for your comments. I will ask my users for logs and update this issue as soon as I receive them.
@jmprieur is it possible that you are referring to issue #1064? I think a MsalCacheCorruptedException would be a good solution for that issue (+ an API to delete the file via the library)

jmprieur · 2019-09-27T16:17:05Z

@tipa : yes, I think they probably have the same root cause. @bgavrilMS do you confirm?

bgavrilMS · 2019-09-30T13:52:54Z

No, this is not the same root cause. There are 2 root causes identified by @tipa :

Reading the token cache from a DPAPI protected file which sometimes gets corrupted (issue GetAccountsAsync() can crash on UWP #1064).
Calling WAB to perform the interactive flow (issue UWP authentication sometimes crashes #1098 - this one)

I plan to tackle the first one by automatically deleting the token cache file, which will result in the user having to re-authenticate (better than uninstalling the app). For the second issue, I am following up with the WAB team to see if a retry mechanism would help.

bgavrilMS · 2019-10-04T13:28:33Z

I added a retry when calling WAB and some information on how to collect logs if this occurs again. It's not a fix per se, but hopefully it will bring us closer to a solution.

jennyf19 · 2019-10-16T00:32:16Z

@tipa @bratsche This is included in the 4.5.0 release.

tipa · 2019-11-21T14:34:42Z

Second, the need more information around the error, i.e. WAB logs. They have pointed at: https://docs.microsoft.com/en-us/windows/win32/secauthn/web-authentication-problems

I now had the case that a user ran into the same problem and he also was able to gather the logs as described in the article linked in the error message. Is there a way I can share the logs with you? I'd prefer not to upload them to Github.

MSAL.UAP.4.7.0.0.MsalClientException: 
ErrorCode: authentication_ui_failed 
Microsoft.Identity.Client.MsalClientException: Web Authentication Broker (WAB) authentication failed. To collect WAB logs, please follow https://aka.ms/msal-net-wab-logs ---> System.IO.FileNotFoundException: The system cannot locate the resource specified. (Exception from HRESULT: 0x800C0005)

jmprieur · 2019-11-21T14:37:15Z

@tipa ; you can send them to me: Jean-Marc dot Prieur at microsoft.com

tipa · 2019-11-21T14:44:18Z

Sure, I've just sent them

charlesroddie · 2020-04-24T16:10:49Z

We are seeing a similar issue on an end-user system. (cc @kevcrooks)

Microsoft.Identity.Client 4.11.0
UWP, WINDOWS 10.0.18362
Desktop, Interactive authentication flow
Using Azure AD B2C
We have provided the internetClient capability.

Expected behaviour: the AcquireTokenInteractive box should appear after the ExecuteAsync() method is called, for the user to log in

Actual behaviour: The box does not appear, and an exception is thrown:

Exception: Microsoft.Identity.Client.MsalClientException
Message: Web Authentication Broker (WAB) authentication failed. To collect WAB logs, please follow https://aka.ms/msal-net-wab-logs
StackTrace: 
Microsoft.Identity.Client.Platforms.uap.WebUI.<AcquireAuthorizationAsync>d__6.MoveNext() + 0x2cb
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Microsoft.Identity.Client.Internal.AuthCodeRequestComponent.<FetchAuthCodeAndPkceInternalAsync>d__6.MoveNext() + 0x202
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Microsoft.Identity.Client.Internal.AuthCodeRequestComponent.<FetchAuthCodeAndPkceVerifierAsync>d__4.MoveNext() + 0xed
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Microsoft.Identity.Client.Internal.Requests.InteractiveRequest.<GetTokenResponseAsync>d__11.MoveNext() + 0x374
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Microsoft.Identity.Client.Internal.Requests.InteractiveRequest.<ExecuteAsync>d__8.MoveNext() + 0x293
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Microsoft.Identity.Client.Internal.Requests.RequestBase.<RunAsync>d__14.MoveNext() + 0x488
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Microsoft.Identity.Client.ApiConfig.Executors.PublicClientExecutor.<ExecuteAsync>d__2.MoveNext() + 0x170
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at [email protected](Unit) + 0x1b
   at FSharp.Control.Tasks.TaskBuilder.tryWith[a](FSharpFunc`2, FSharpFunc`2) + 0x3b

Is this the same issue or shall I post a new issue @jmprieur ? Is there no way to get WAB to report a useful exception?

bgavrilMS · 2020-04-24T16:24:23Z

@charlesroddie - please log a separate issue

charlesroddie · 2020-04-25T19:06:42Z

@bgavrilMS done #1782

bgavrilMS · 2020-05-07T13:09:46Z

@tipa - it looks like the WAB error is because it cannot reach the ping-sso url

AuthHost encountered a navigation error at URL: <https://ping-sso.schneider-electric.com/idp/eyJ2c2lkIjoic2UuY29tIn0=/prp.wsf?client-request-id=c07c1ec.........

 HR_INET_E_RESOURCE_NOT_FOUND

A few thoughts:

we do not collect exception messages in the logs by default, because they could contain personal identifiable information (PII)
it's possible that WAB had a nicer error message for you in the inner exception, but this was not logged
if possible, enable PII logging
problem might be external to WAB and related to VPN. You should be able to craft an authroziation url on your own and observe if you can navigate to it.
I'll work with the WAB team to see if we can improve the experience.

tipa · 2020-05-07T13:33:52Z

Thanks for looking into it. This was quite an old log, once I have another user who is experiencing this and willing to collect the (PII) logs, I send them in.

jmprieur added documentation scenario:Mobile-UWP labels Apr 20, 2019

bgavrilMS self-assigned this Sep 9, 2019

bgavrilMS changed the title ~~Clarify needed capabilites for UWP~~ UWP authentication sometimes crashes Sep 18, 2019

bgavrilMS added bug and removed documentation labels Sep 18, 2019

jmprieur added this to the 4.4.1 milestone Sep 26, 2019

jmprieur added the Fixed label Oct 3, 2019

bgavrilMS added In Progress and removed Fixed labels Oct 4, 2019

bgavrilMS added a commit that referenced this issue Oct 4, 2019

Retry calls to WAB and better error message - #1098

07f0968

bgavrilMS added Fixed and removed In Progress labels Oct 4, 2019

jennyf19 modified the milestones: 4.4.1, 4.5 Oct 9, 2019

jennyf19 closed this as completed Oct 16, 2019

tipa mentioned this issue May 3, 2020

UWP authentication crash ((WAB) authentication failed) #1782

Closed

tipa mentioned this issue Sep 29, 2020

[Feature Request] Make it easier for developers to enable "SSO" on UWP #1901

Closed

vidya091209 mentioned this issue Nov 13, 2020

UWP AuthHost encountered a navigation error at URL: https://xxx.b2clogin.com/xxx.onmicrosoft.com/oauth2/authresp with StatusCode: 0x800C000D. #2188

Closed

1 task

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

UWP authentication sometimes crashes #1098

UWP authentication sometimes crashes #1098

tipa commented Apr 19, 2019

tipa commented Sep 6, 2019

bgavrilMS commented Sep 9, 2019

tipa commented Sep 9, 2019

tipa commented Sep 17, 2019

bgavrilMS commented Sep 17, 2019

bgavrilMS commented Sep 17, 2019

tipa commented Sep 18, 2019

bgavrilMS commented Sep 18, 2019

jmprieur commented Sep 18, 2019

tipa commented Sep 18, 2019

bgavrilMS commented Sep 26, 2019

jmprieur commented Sep 26, 2019 •

edited

Loading

tipa commented Sep 27, 2019

jmprieur commented Sep 27, 2019

bgavrilMS commented Sep 30, 2019

bgavrilMS commented Oct 4, 2019

jennyf19 commented Oct 16, 2019

tipa commented Nov 21, 2019

jmprieur commented Nov 21, 2019

tipa commented Nov 21, 2019

charlesroddie commented Apr 24, 2020 •

edited

Loading

bgavrilMS commented Apr 24, 2020

charlesroddie commented Apr 25, 2020

bgavrilMS commented May 7, 2020

tipa commented May 7, 2020

UWP authentication sometimes crashes #1098

UWP authentication sometimes crashes #1098

Comments

tipa commented Apr 19, 2019

tipa commented Sep 6, 2019

bgavrilMS commented Sep 9, 2019

tipa commented Sep 9, 2019

tipa commented Sep 17, 2019

bgavrilMS commented Sep 17, 2019

bgavrilMS commented Sep 17, 2019

tipa commented Sep 18, 2019

bgavrilMS commented Sep 18, 2019

jmprieur commented Sep 18, 2019

tipa commented Sep 18, 2019

bgavrilMS commented Sep 26, 2019

jmprieur commented Sep 26, 2019 • edited Loading

tipa commented Sep 27, 2019

jmprieur commented Sep 27, 2019

bgavrilMS commented Sep 30, 2019

bgavrilMS commented Oct 4, 2019

jennyf19 commented Oct 16, 2019

tipa commented Nov 21, 2019

jmprieur commented Nov 21, 2019

tipa commented Nov 21, 2019

charlesroddie commented Apr 24, 2020 • edited Loading

bgavrilMS commented Apr 24, 2020

charlesroddie commented Apr 25, 2020

bgavrilMS commented May 7, 2020

tipa commented May 7, 2020

jmprieur commented Sep 26, 2019 •

edited

Loading

charlesroddie commented Apr 24, 2020 •

edited

Loading