Following this manual precisely step by step result to the "AADB2C90037: An error occurred while processing the request. Please contact administrator of the site you are trying to access." during the last step of the userflow testing.
What is missing in the manual?
Thanks.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@mrvladis, thank you for reaching out. We are looking into this and would get back to you soon on this thread.
@mrvladis The instructions are working fine for me. I just double checked by configuring the policy again in my B2C tenant and didn't encounter any such issue. There seems to be some configuration issue which is causing this error. Could you please share your policy files at AzCommunity[at]microsoft[dot]com to investigate into it?
@amanmcse
I am not arguing that instructions may work for you, but looking on how many people getting exactly the same error - can't confirm that instructions are written in the best possible way.
I don't believe that the whole purpose of this document is to demonstrate that it is working for you, but to make sure it is working for people doing it for the first time and understand what and why need's to be done.
As such, at the beginning of the article you have a section "Prerequisites" you have a reference to the other part of the documentation:
"Complete the steps in Get started with custom policies in Azure Active Directory B2C."
That section is quite specific about what files you need to use, as it says "In this article, you edit the XML custom policy files in the SocialAndLocalAccounts starter pack. "
Now, I have completed and used it. And I want to implement Azure AD.
"Register the claims provider" section just says Open the TrustFrameworkBase.xml file from the starter pack.. My and probably other users perception that this falls under "SocialAccounts ". Here you might be lucky, if you still need local accounts and you will choose SocialAndLocalAccounts . In my case - I didn't, so for me manual resulted in to the above error.
Lucky - I have decided to try SocialAndLocalAccounts and it worked.
The other point that I have is around Visual Studio Code. Articles in this section suggest to use it and even make a reference Visual Studio code B2C extension. I can see that it is a 3rd party extension and it gives a different XML structure for the Azure AD Claim provider, comparing to the one in the article. Which also expect ClaimeID from the source Azure AD.
This would also confuse the end users.
Hope this make sense.
Thanks,
@mrvladis If you are saying "federating Azure AD with B2C via custom policy works only with SocialAndLocalAccounts starter pack and not with SocialAccounts", you have come to a wrong conclusion here.
Azure AD is added as Social(federated IDP) and it doesn't need any parameters for Local Accounts in the policy files. The instructions in this document are same for SocialAccounts, SocialAndLocalAccounts & SocialAndLocalAccountsWithMFA starter packs and works the same way.
I still believe the error was due to some misconfiguration in your policy files. Feel free to tag me in your reply if you have any further questions.
@amanmcse I think there is a difference in-between it should and it is.
If it would be as simple as you say - there wouldn't be so many people getting this error.
In my case - I am quite confident in the cause, as there was no syntax errors in XML (all files were uploaded successfully) and when transitioning to SocialAndLocalAccounts - I only copied updated lines.
May be if I've used "SocialAccounts" from the very begging, ignoring statement in "Complete the steps in Get started with custom policies in Azure Active Directory B2C." section to use SocialAndLocalAccounts - it could have worked, but again, I was doing it for the first time and was following the guidance.
Even the error itself - could be made more explanatory or being part of the documentation, so people do not struggle.
I don't have any mean to keep arguing on the matter. If you guys think that it is all good as is - it is up to you.
Luckily there are many other competitive products available on the market, that may have more user friendly documentation, so people wouldn't be struggling for a long time with strange errors, before they go with other product.
Thanks.
@mrvladis Thank you for your feedback. I agree with you that the error could be more descriptive and you can share your feedback at https://feedback.azure.com regarding this.
At this point, we don't know the cause of the issue and unable to reproduce the issue at our end. Which is why it is difficult to update the document with instructions to avoid that error. Hope you would understand. I will try to gather more details about this issue and update the document to avoid this error once I have required details
Closing the thread for now.
Most helpful comment
@amanmcse I think there is a difference in-between it should and it is.
If it would be as simple as you say - there wouldn't be so many people getting this error.
In my case - I am quite confident in the cause, as there was no syntax errors in XML (all files were uploaded successfully) and when transitioning to SocialAndLocalAccounts - I only copied updated lines.
May be if I've used "SocialAccounts" from the very begging, ignoring statement in "Complete the steps in Get started with custom policies in Azure Active Directory B2C." section to use SocialAndLocalAccounts - it could have worked, but again, I was doing it for the first time and was following the guidance.
Even the error itself - could be made more explanatory or being part of the documentation, so people do not struggle.
I don't have any mean to keep arguing on the matter. If you guys think that it is all good as is - it is up to you.
Luckily there are many other competitive products available on the market, that may have more user friendly documentation, so people wouldn't be struggling for a long time with strange errors, before they go with other product.
Thanks.