Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validation errors do not communicate reason for failed validation #55

Open
millicandavid opened this issue Jul 23, 2019 · 1 comment
Open

Comments

@millicandavid
Copy link

millicandavid commented Jul 23, 2019

Does anyone have any advice on troubleshooting validation errors? I tried setting up Application Insights for my tenant but all I see is a generic message

"Error returned was 400/Request_BadRequest: One or more property values specified are invalid."

I had a working setup based on the starter pack. All I did was add a companyName field on signup and it fails validation. I posted more info at https://stackoverflow.com/questions/57186366/how-to-troubleshoot-validation-errors-in-azure-active-directory-b2c-custom-attri

@xinaxu
Copy link
Contributor

xinaxu commented Jan 28, 2020

That is the exact response returned from AAD Graph API. We don't yet log the request sent to Graph so we don't know which property has invalid value. But we are planning to enhance the debugability and logging experience so this kind of issue will be easier to troubleshoot in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants