firebase-js-sdk icon indicating copy to clipboard operation
firebase-js-sdk copied to clipboard

Microsoft Auth Errors on Account Creation

Open scottfr opened this issue 5 years ago • 9 comments

[REQUIRED] Describe your environment

  • Operating System version: OSX
  • Browser version: Chrome 73
  • Firebase SDK version: Web 5.8.4
  • Firebase Product: auth

[REQUIRED] Describe the problem

When I attempt to create an account using the new Microsoft auth I receive this error:

Failed to fetch resource from https://graph.microsoft.com/v1.0/me, http status: 202, http response: {"@odata.context":"https://graph.microsoft.com/v1.0/$metadata#users/$entity","id":"XYZ","userPrincipalName":"[email protected]","businessPhones":[],"displayName":null,"jobTitle":null,"mail":null,"mobilePhone":null,"officeLocation":null,"preferredLanguage":null}

Note: I've redacted the id and userPrincipalName name here.

The Firebase account is actually created successfully (even though it doesn't log me in after the creation process) but properties like emailVerified are not set on the account. After the initial error, I am able to log into the newly created account via Microsoft login.

scottfr avatar Apr 06 '19 10:04 scottfr

Please file a ticket at https://firebase.google.com/support/ You will need to provide sensitive project related information not appropriate for this public forum.

bojeil-google avatar Apr 06 '19 18:04 bojeil-google

I've submitted a bug report. The id is [2-3290000025831]

scottfr avatar Apr 07 '19 14:04 scottfr

I am experiencing the same issue. Is there a workaround for this?

hoggetaylor avatar Oct 22 '19 17:10 hoggetaylor

This is currently working as expected as the backend checks the HTTP status code in the response. In this case, the response code is 202, Accepted while expected behavior is 200, OK. I think Microsoft side should respond with 200 if the response is already constructed.

While this is currently an expected limitation, we'll treat this as a feature request and keep this open. Thank you!

rommelpe avatar Nov 08 '19 11:11 rommelpe

Is there any update on this issue? I'm running into the same problem. Is there any workaround besides that our users have to login twice for the first time?

christianwiese avatar Jun 22 '20 13:06 christianwiese

For internal tracking: b/130400078

As rommelpe mentioned, this seems like Microsoft should be responding with a 200. 202 doesn't imply completion. I am unaware of any workaround at the moment but will ask around.

scottcrossen avatar Jun 24 '20 03:06 scottcrossen

Is there any update on this issue? I still facing this issue.

andorsch avatar Oct 28 '20 19:10 andorsch

I am experiencing this issue as well, any updates?

AlexanderChiclana avatar Feb 24 '22 21:02 AlexanderChiclana

Any update on this issue? I am still facing the same

ShyamVashista avatar Jul 25 '22 08:07 ShyamVashista