ContinueOnError true has no effect

kirill.kolesnikov 21 Reputation points
2022-05-13T11:56:34.827+00:00

In extesntion I'm overrided SelfAsserted-LocalAccountSignin-Email profile

<TechnicalProfile Id="SelfAsserted-LocalAccountSignin-Email">
<ValidationTechnicalProfiles>
<!-- Initiate a normal logon against Azure AD B2C -->
<ValidationTechnicalProfile ReferenceId="login-NonInteractive" ContinueOnError="true" />
<!-- Check if account is locked out. Note: This validation technical profile also return the bad user name and password -->
<ValidationTechnicalProfile ReferenceId="REST-AccountLockout">
<Preconditions>
<Precondition Type="ClaimEquals" ExecuteActionsIf="false">
<Value>objectId</Value>
<Value>badPassword</Value>
<Action>SkipThisValidationTechnicalProfile</Action>
</Precondition>
</Preconditions>
</ValidationTechnicalProfile>
</ValidationTechnicalProfiles>
</TechnicalProfile>

Blockquote

and added default value for oid in login-NonInteractive
<TechnicalProfile Id="login-NonInteractive">
<InputClaims>
<!--Replace with your Application ID of the ProxyIdentityExperienceFramework-->
<InputClaim ClaimTypeReferenceId="client_id" DefaultValue="{ProxyIdentityExperienceFramework}" />
<InputClaim ClaimTypeReferenceId="resource_id" PartnerClaimType="resource" DefaultValue="{IdentityExperienceFramework}" />
</InputClaims>
<OutputClaims>
<OutputClaim ClaimTypeReferenceId="objectId" PartnerClaimType="oid" DefaultValue="badPassword"/>
</OutputClaims>
</TechnicalProfile>

Blockquote

But if the credentials are not correct, I never get into the next validation profile

Microsoft Entra External ID
Microsoft Entra External ID
A modern identity solution for securing access to customer, citizen and partner-facing apps and services. It is the converged platform of Azure AD External Identities B2B and B2C. Replaces Azure Active Directory External Identities.
2,633 questions
0 comments No comments
{count} votes

Accepted answer
  1. 2022-05-26T07:12:57.657+00:00

    Hello @kirill.kolesnikov , please ensure the metada entry for grant_type is not present (remove or comment it) in the login-NonInteractive Technical Profile (Usually stored in the TrustFrameworkBase policy).

    Let us know if this answer was helpful to you or if you need additional assistance. If it was helpful, please remember to accept it so that others in the community with similar questions can more easily find a solution.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. 2022-05-15T01:51:08.803+00:00

    Hello @kirill.kolesnikov , REST-AccountLockout is being skipped due to its precondition: objectId claim value is never set to badPassword.

    Let us know if this answer was helpful to you. If so, please remember to accept it so that others in the community with similar questions can more easily find a solution.