Best gaming deals on Amazon | This weeks Xbox deals with gold

Windows Hello for Business PIN Provision Error 0x801C03ED

Category: azure windowsazuread

Question

we10 on Sat, 12 May 2018 07:29:17


Any Help to solve this issue will be appreciated. Thank You In Advance

Encountered error during OAuth authorization request.
Additional Data
Exception details:
Microsoft.IdentityServer.Web.Protocols.OAuth.Exceptions.OAuthInvalidResourceException: MSIS9329: Received invalid OAuth request. The 'resource' parameter's value does not correspond to any valid registered relying party. Received resource: 'urn:aad:tb:update:prt'.
   at Microsoft.IdentityServer.Web.Protocols.OAuth.OAuthAuthorization.OAuthAuthorizationRequestContext.ValidateCore()

ERROR NUMBER TWO

Encountered error during federation passive request.
Additional Data
Protocol Name:
OAuthAuthorizationProtocol
Relying Party:
urn:aad:tb:update:prt
Exception details:
Microsoft.IdentityServer.Web.Protocols.OAuth.Exceptions.OAuthInvalidResourceException: MSIS9329: Received invalid OAuth request. The 'resource' parameter's value does not correspond to any valid registered relying party. Received resource: 'urn:aad:tb:update:prt'.
   at Microsoft.IdentityServer.Web.Protocols.OAuth.OAuthAuthorization.OAuthAuthorizationRequestContext.ValidateCore()
   at Microsoft.IdentityServer.Web.Protocols.ProtocolContext.Validate()
   at Microsoft.IdentityServer.Web.Protocols.OAuth.OAuthAuthorization.OAuthAuthorizationProtocolHandler.GetRequiredPipelineBehaviors(ProtocolContext pContext)
   at Microsoft.IdentityServer.Web.PassiveProtocolListener.EvaluateHomeRealm(PassiveProtocolHandler protocolHandler, ProtocolContext protocolContext)
   at Microsoft.IdentityServer.Web.PassiveProtocolListener.OnGetContext(WrappedHttpListenerContext context)

Replies

Ajay Kadam on Sat, 12 May 2018 09:53:21


The error code 0x801c03ed could be caused because Multi-factor authentication is required for a 'provisionkey' operation but was not performed or Token was not found in the Authorization header or Failed to read one or more objects, or the request sent to the server was invalid. You can overcome this error by Sign out and then sign in again. If that doesn't resolve the issue, unjoin the device from Azure Active Directory (Azure AD) and rejoin. Refer: Windows Hello errors during PIN creation

--------------------------------------------------------------------------------------

If this answer was helpful, click “Mark as Answer” or Up-Vote. To provide additional feedback on your forum experience, click here

Latest posts in the category


general office development

kinect for windows v2 sdk