error is always displayed on Azure AD B2C, why?

By -

I am trying to display a custom error, idea is user may have several MFA setup, user introduces login, then goes to a screen where he needs to select the MFA that he wants to use, if the MFA is in a list, then he can proceed, if it is not, then we need to display an error. This is my code:

...

<OrchestrationStep Order="3"
                                   Type="ClaimsExchange"
                                   ContentDefinitionReferenceId="api.selfasserted">
                    <ClaimsExchanges>
                        <ClaimsExchange Id="MFAConfigChecks"
                                        TechnicalProfileReferenceId="SelfAsserted-GettingSelectedMFAParameter" />
                    </ClaimsExchanges>
                </OrchestrationStep>

...

 <TechnicalProfile Id="SelfAsserted-GettingSelectedMFAParameter">
                <DisplayName>Getting selected MFA Parameter</DisplayName>
                <Protocol Name="Proprietary"
                          Handler="Web.TPEngine.Providers.SelfAssertedAttributeProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
                <Metadata>
                    <Item Key="ContentDefinitionReferenceId">api.selfasserted</Item>
                    <Item Key="UserMessageIfClaimsTransformationBooleanValueIsNotEqual">testeando.</Item>
                </Metadata>
                <IncludeInSso>false</IncludeInSso>
                <InputClaims>
                    <InputClaim ClaimTypeReferenceId="preferredAuthenticationMethodCollection" />
                    <InputClaim ClaimTypeReferenceId="NoMFAConfig" />
                </InputClaims>
                <OutputClaims>
                    <OutputClaim ClaimTypeReferenceId="selectedAuthenticationMethod"
                                 Required="true" />

                </OutputClaims>
                <OutputClaimsTransformations>

                    <OutputClaimsTransformation ReferenceId="SelectedMFAIsConfigured" />
                    <OutputClaimsTransformation ReferenceId="NeedToDisplayError" />

                </OutputClaimsTransformations>
                <ValidationTechnicalProfiles>
                    <ValidationTechnicalProfile ReferenceId="AssertBooleanSelectedMFAError" />
                </ValidationTechnicalProfiles>
            </TechnicalProfile>

...

<TechnicalProfile Id="AssertBooleanSelectedMFAError">
                    <DisplayName>Unit test</DisplayName>
                    <Protocol Name="Proprietary"
                              Handler="Web.TPEngine.Providers.ClaimsTransformationProtocolProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
                    <OutputClaims>
                        <OutputClaim ClaimTypeReferenceId="AreConditionsMet"
                                     DefaultValue="false" />
                    </OutputClaims>
                    <OutputClaimsTransformations>
                        <OutputClaimsTransformation ReferenceId="MFAConditionsMet" />
                    </OutputClaimsTransformations>
                    <UseTechnicalProfileForSessionManagement ReferenceId="SM-Noop" />
                </TechnicalProfile>

I have tested so far for AreConditionsMet and at this stage, when this is true the error is still being display, what am I doing wrong? I think it is taking the default value in any case, but I don't get why it does not workout the value in the SelfAsserted-GettingSelectedMFAParameter technical profile.

<ClaimsTransformation Id="MFAConditionsMet"
                              TransformationMethod="AssertBooleanClaimIsEqualToValue">
            <InputClaims>
                <InputClaim ClaimTypeReferenceId="AreConditionsMet"
                            TransformationClaimType="inputClaim" />
            </InputClaims>
            <InputParameters>
                <InputParameter Id="valueToCompareTo"
                                DataType="boolean"
                                Value="true" />
            </InputParameters>
        </ClaimsTransformation>


Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more