Bug in the custom login for Azure ADB2C?

Bug reports
1

Hi,

I’m trying to get authentication with AdB2c to work. I have followed the guide given in the doc : (Implement third-party authentication | Appfarm Documentation). This seems to work, but the challenge is that when trying to log in , the URL generated by the AppFarm App looks like this :
https://domain.b2clogin.com/domain.onmicrosoft.com/oauth2/v2.0/authorize?p=custom_policy?client_id=cbdc86b8-df8e-40fe-944e-255c84d04929…

This URL is not a valid authentication URL for AdB2c, as you can see it contains two “?” ! The last one should be and ampersand, so the URL should look like this to be valid :

https://domain.b2clogin.com/domain.onmicrosoft.com/oauth2/v2.0/authorize?p=custom_policy&client_id=cbdc86b8-df8e-40fe-944e-255c84d04929…

2

Hello!

Good find. This is a bug, and we have located it! Patch is coming soon.

Will keep you posted.

3

This one is now reportedly fixed! Can you check if the problem is solved?

4

Hi Kristian,

Impressive fix time. Yes , I can confirm that the ADB2c login now works.

Thank you.