Question

Solved1.27K views6th October 2022authentication Azure B2C SAML

1

Jens Vandewalle [SLC] [DevOps Enabler]9.29K 30th September 2022 1 Comment

Hi Dojo,

I have a system that authenticates through Azure B2C via SAML.

I noticed that the login behavior is different between web and Cube. Why is that?

Web
I need to authenticate with my phone even while I have configured to stay signed in.

Cube
I don't need to authenticate with my phone anymore

Alberto De Luca [DevOps Enabler] Posted new comment 6th October 2022

Alberto De Luca [DevOps Enabler] commented 6th October 2022

Just leaving this feature suggestion as a comment: led to think that if the SSO is in place with the SAML at client layer, I’d expect no log-in is required, regardless of the specific client app (browser/desktop):

https://community.dataminer.services/new-feature-suggestions/saml-single-sign-on-sso-to-dataminer-for-users-already-authenticated-in-azuread-via-the-os/

1 Answer

Just leaving this feature suggestion as a comment: led to think that if the SSO is in place with the SAML at client layer, I’d expect no log-in is required, regardless of the specific client app (browser/desktop):

https://community.dataminer.services/new-feature-suggestions/saml-single-sign-on-sso-to-dataminer-for-users-already-authenticated-in-azuread-via-the-os/

score 4 · Answer 1 · 2022-09-30T06:35:19+00:00

Hi Jens,

Ultimately it is up to the IdentityProvider web service (Microsoft Azure in this scenario) to decide which authentication steps are required. We have seen different behavior based on IP address, browser UserAgent, user security level or even after X amount of logins. As long as the browser allows cookies, javascript is enabled and is not in incognito/private mode (i.e. be as compliant as possible), there is probably not much you can do about this behavior.

Azure B2C Login behavior

1 Answer