Through Rest API we are validating PhoneNumber and if PhoneNumber Exists we Pass Error Message in JSON but it is not showing

Question

Through Rest API we are validating PhoneNumber and if PhoneNumber Exists we Pass Error Message in JSON but it is not showing

Rajadurai V 45

@AmanpreetSingh-MSFT @Jas Suri @James Hail @Marilee Turscak-MSFT

we are trying to validate the PhoneNumber through REST API call. if the PhoneNumber Already Exists we send a JSON As Per Doc. sample JSON Structure below.

{
  "version": "1.0.0",
  "statusCode": 409,
  "userMessage": "User already exist with this phone number"
}

but it throws Error Message like below

'AF-PhoneNumberValidation' specified in step '3' returned HTTP error response with Code 'Conflict' and Reason 'Conflict'.

Below is the Rest API Call

<ClaimsProvider>
            <DisplayName>HTTP Request Technical Profiles</DisplayName>
            <TechnicalProfiles>
                <TechnicalProfile Id="AF-PhoneNumberValidation">
                    <DisplayName> Phone Number Validation </DisplayName>
                    <Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.RestfulProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
                    <Metadata>
                        <Item Key="ServiceUrl">URL</Item>
                        <Item Key="SendClaimsIn">Body</Item>
                        <Item Key="AuthenticationType">None</Item>
                        <Item Key="AllowInsecureAuthInProduction">true</Item>
                        <Item Key="HttpBinding">POST</Item>
                        <Item Key="IncludeClaimResolvingInClaimsHandling">true</Item>
                    </Metadata>
                    <InputClaims>
                        <InputClaim ClaimTypeReferenceId="extension_phoneNumber"  PartnerClaimType="phoneNumber"/>
                    </InputClaims>
                </TechnicalProfile>
            </TechnicalProfiles>
    </ClaimsProvider>

calling this Technical Profile

<ValidationTechnicalProfiles>
            <ValidationTechnicalProfile ReferenceId="AF-PhoneNumberValidation" ContinueOnError="false"/>
            <ValidationTechnicalProfile ReferenceId="AAD-UserWriteUsingLogonEmail" />
          </ValidationTechnicalProfiles>

Please let me know if we have missed out anything.

Thanks,

Rajadurai.

Jas Suri 91 Reputation points Microsoft Employee

2023-06-22T13:57:51.0533333+00:00

Do you mean that the error is sent back to the app? Instead of what is expected, which would be to return an error to the screen?

If this REST API tech profile is called from a validation technical profile from a selfasserted tech profile, then the error should come up on screen. If there is no page visible to the user when the API is called, then the error will go back to the app.

Rajadurai V 45

@Jas Suri

This is the technical Profile where i call the Validation Profile. can you please check and let me know if this is right.

<TechnicalProfile Id="LocalAccountSignUpWithReadOnlyEmail">
          <DisplayName>Email signup</DisplayName>
          <Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.SelfAssertedAttributeProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
          <Metadata>
            <Item Key="IpAddressClaimReferenceId">IpAddress</Item>
            <Item Key="ContentDefinitionReferenceId">api.localaccountsignup</Item>
            <Item Key="language.button_continue">Sign Up</Item>
            <!-- Sample: Remove sign-up email verification -->
            <Item Key="EnforceEmailVerification">False</Item>
          </Metadata>
          <InputClaimsTransformations>
            <InputClaimsTransformation ReferenceId="CreateReadonlyEmailClaim" />
          </InputClaimsTransformations>
          <InputClaims>
            <!--Sample: Set input the ReadOnlyEmail claim type to prefilled the email address-->
            <InputClaim ClaimTypeReferenceId="readOnlyEmail" />
          </InputClaims>
          <OutputClaims>
            <OutputClaim ClaimTypeReferenceId="objectId" />
            <!-- Sample: Display the ReadOnlyEmail claim type (instead of email claim type)-->
            <OutputClaim ClaimTypeReferenceId="readOnlyEmail" Required="true" />
            <OutputClaim ClaimTypeReferenceId="newPassword" Required="true" />
            <OutputClaim ClaimTypeReferenceId="reenterPassword" Required="true" />
            <OutputClaim ClaimTypeReferenceId="executed-SelfAsserted-Input" DefaultValue="true" />
            <OutputClaim ClaimTypeReferenceId="authenticationSource" />
            <OutputClaim ClaimTypeReferenceId="newUser" />
            <OutputClaim ClaimTypeReferenceId="extension_userName" />
            <OutputClaim ClaimTypeReferenceId="extension_phoneNumber" /> 

          </OutputClaims>
          <ValidationTechnicalProfiles>
            <ValidationTechnicalProfile ReferenceId="AF-PhoneNumberValidation" ContinueOnError="false"/>
            <ValidationTechnicalProfile ReferenceId="AAD-UserWriteUsingLogonEmail" />
          </ValidationTechnicalProfiles>
          <!-- Sample: Disable session management for sign-up page -->
          <UseTechnicalProfileForSessionManagement ReferenceId="SM-Noop" />
        </TechnicalProfile>

Need to get the below Error Message in the Sign up Page

"User already exist with this phone number"

but we are getting

"AF-PhoneNumberValidation' specified in step '3' returned HTTP error response with Code 'Conflict' and Reason 'Conflict".

Thanks,

Rajadurai.

1 answer

Your answer

Jas Suri 91 Reputation points Microsoft Employee

2023-06-22T13:57:51.0533333+00:00

Do you mean that the error is sent back to the app? Instead of what is expected, which would be to return an error to the screen?

If this REST API tech profile is called from a validation technical profile from a selfasserted tech profile, then the error should come up on screen. If there is no page visible to the user when the API is called, then the error will go back to the app.

Answer 1

Jas Suri 91 Microsoft Employee

Follow this: https://learn.microsoft.com/en-us/azure/active-directory-b2c/restful-technical-profile#error-handling

You canb change the error message displayed by making your API respond in the following way:

{
  "version": "1.0.0",
  "status": 409,
  "code": "API12345",
  "requestId": "50f0bd91-2ff4-4b8f-828f-00f170519ddb",
  "userMessage": "
  "developerMessage": "Verbose description of problem and how to fix it.",
  "moreInfo": "https://restapi/error/API12345/moreinfo"
}

Rajadurai V 45 Reputation points

2023-06-22T15:52:55.4533333+00:00
@Jas Suri

Already we are returning the response in JSON. find below the response

{ "version": "1.0.0", "statusCode": 409, "userMessage": "User already exist with this phone number" }

Http Status code also we are sending it as 409(conflict).

it is not working. it is giving below Error

"AF-PhoneNumberValidation' specified in step '3' returned HTTP error response with Code 'Conflict' and Reason 'Conflict".
Rajadurai V 45 Reputation points

2023-06-23T03:25:27.4133333+00:00
@Jas Suri

Already we are returning the response in below JSON format. but still it is not working.it is still showing the Error Message -

"AF-PhoneNumberValidation' specified in step '3' returned HTTP error response with Code 'Conflict' and Reason 'Conflict".

but we need to show the customized Error Message "User Already Exist With this phone number".

can you please let me know if we are missing anything.

Response in JSON format:

{ "version": "1.0.0", "statusCode": 409, "userMessage": "User already exist with this phone number" }
Rajadurai V 45 Reputation points

2023-06-23T04:25:58.74+00:00

@Jas Suri
Rajadurai V 45 Reputation points

2023-06-23T04:43:45.1566667+00:00
@Jas Suri

Have followed the same in the document and the response in JSON Format is below

{ "version": "1.0.0", "statusCode": 409, "userMessage": "User already exist with this phone number" }

but we are getting the below Exception

is there anything we need do it in Error Handling configuration.

Please let me know. it is urgent.

Thanks,

Rajadurai.

Share via

Through Rest API we are validating PhoneNumber and if PhoneNumber Exists we Pass Error Message in JSON but it is not showing

1 answer

Your answer