-
Notifications
You must be signed in to change notification settings - Fork 599
I have followed all the steps trying to configure email invite signup custom policy flow. But I'm facing issue that id_token_hint cannot be decoded with custom policy failing at GetRelyingPartyInputClaimsHandler, with error message in Insights trace
"Unexpected character encountered while parsing value: <. Path '', line 0, position 0."
This is happening in the first Orchestration step IdTokenHint_ExtractClaims.
Signup link is generated from WebApi which is registered as AppService in Azure, I have uploaded pfx certificate to AppService, set up cert thumbprint values (WEBSITE_LOAD_CERTIFICATES as well), in IdentityExperienceFramework created new policy key from same certificate, used that policy key in base xml file, but nothing helps. ClientID values are set up correctly.
All issues are pointing that adb2c cannot decode JWT id_token_hint, but I'm unaware why is that. I have used self signed certificate that I have created on my localhost, could it be due this?
When using jwt.ms id_token_hint is well formed, .well-known/openid-configuration is accessible.
All reactions
Well the problem was in my OidcController in .well-known/openid-configuration endpoint where I had a typo in JwksUri and missed '/' before '.well-known/keys' of course this caused that id_token_hint could not be decoded on ADB2C side....
Replies: 1 comment
Well the problem was in my OidcController in .well-known/openid-configuration endpoint where I had a typo in JwksUri and missed '/' before '.well-known/keys' of course this caused that id_token_hint could not be decoded on ADB2C side....