Question about example "B2C IEF Custom Policy - A Sign In policy with Home Realm Discovery"

[glomaga]

Question about example "B2C IEF Custom Policy - A Sign In policy with Home Realm Discovery"

[JasSuri]

Wouldn't it be confusing for federated users, because they dont have a password with B2C? And then if they are redirected to the federated IdP, they then have to enter the password again? Its why I decided to separate username/password over 2 pages.

You are getting this error since you are referencing an OIDC Technical Profile from an Orchestration step. This instructs B2C to do a federation redirect rather than the backend ROPC call as part of a validation technical profile. Login-noninteractive will need to be called from a validation technical profile, its a special case.

[glomaga]

Thanks for your answer was very helpful, I found a way to do it from the technical profile on SelfAsserted-Signin-Email:
ValidationTechnicalProfile ReferenceId="login-NonInteractive">
Preconditions>
Precondition Type="ClaimEquals" ExecuteActionsIf="true">
Value>isKnownCustomer
Value>True
Action>SkipThisValidationTechnicalProfile
Precondition>
Preconditions>
ValidationTechnicalProfile>
About the enter the password twice for external provider, I am reviewing the possibility to control that on the UI with JS, if the domain for the email is = to the External Provider, don't enable the password field, and sent to IEF dummy password to be able to continue the flow.