Azure B2C login issues

E-mail notifications

Adrian Ursu

Posted on 09/11/2021 13:18:12

Hi guys,

I have a solution that is supposed to be using the Azure AD B2C external authentication.

I have configured 2 environments: Dev and Production using Dynamicweb 9.10.12.

I have configured both the same way, only with different sets of credentials. Everything works pretty well so far.

I have then upgraded the production version to 9.12.2. After the upgrade, the authentication does not happen anymore unless you visit the external authentication link: /Admin/Public/Social/ExternalLogin.aspx?action=login&providerID=2

While running on 9.10.12, the authentication happened seamlessly.

I have tested again by changing the version back to 9.10.12 and it seems that the authentication works well again.

What can be the issue between these 2 versions? Am I missing a 9.12 specific setting? A web.config record? Or is it a bug?

One more thing that I have noticed is that by using the "logout function": /Admin/Public/ExtranetLogoff.aspx?ID=8065, I get a pretty nasty error:

IDX20108: The address specified '[PII is hidden. For more details, see https://aka.ms/IdentityModel/PII.]' is not valid as per HTTPS scheme. Please specify an https address for security reasons. If you want to test with http address, set the RequireHttps property on IDocumentRetriever to false.
Parameter name: address

I am not sure if this is related to the "Logout from Azure on extranet logout" checkbox on my configuration. I have tried with both options (on and off) and I get the same error. It can be, however, related to how the entire Azure B2C authentication is configured in Microsoft Azure.

Thank you,

Adrian

Replies

Oleg Rodionov

Posted on 10/11/2021 06:19:16

I've checked the issue on both last DW9.10.17 and DW9.12.3. I see it's possible to login by the provider using /Admin/Public/Social/ExternalLogin.aspx?action=login&providerID=4 (external user can be created) but exception occurs on performin the "logout function". It's other than yours (find the attachment) but, perhaps have the same sense I suppose. I've created new BUG 5620 againt the issue to research and fix.

BR, Oleg QA

Adrian Ursu

Posted on 25/11/2021 17:12:44

Hi Oleg,

Thank you and I apologize for the late message.

Can you also check the behavior of the auto-login between 9.10.x and 9.10.12?

In my case, 9.10.x behaves correctly (as expected) while 9.12.x requires an explicit access of the ExternalLogin.aspx link.

Because of this, we had to downgrade the solution to 9.10.

Thank you,

Adrian

Oleg Rodionov

Posted on 26/11/2021 03:08:42

Hi Adrian

5620 has been fixed in DW9.12.4 has recently been released (with Dynamicweb.Environment 4.0.7, Dynamicweb 9.12.13, Dynamicweb.Environment.Web 3.2.2). Please, check your issue on the admin version and provide exact steps of your scenario if still reproducable. Thanks.

BR, Oleg QA

Adrian Ursu

Posted on 26/11/2021 10:19:19

Hi Oleg,

Thank you very much.

I will try it out.

Adrian

You must be logged in to post in the forum

Developer forum

Azure B2C login issues

Replies