with b2c custom policy, capture checkbox state during profile editing

Question

with b2c custom policy, capture checkbox state during profile editing

Steve Bi 0

We have b2c custom policy, we have checkbox to give user options on "Agree to receive email..." checkbox implemented with CheckboxMultiSelect as the only option, it capture value for the first time. But when user later on uncheck the checkbox, the value can not updated anymore.

1 answer

Your answer

Answer 1

James Hamil 27,211 Microsoft Employee Moderator

Hi @Steve Bi , you'll have to use a Persisted Claim element in your custom policy. This element allows you to store the value of the checkbox in the user's profile, so that it can be retrieved and updated later. For example from the document:

<PersistedClaims>
  <PersistedClaim ClaimTypeReferenceId="email" PartnerClaimType="signInNames.emailAddress" />
  <PersistedClaim ClaimTypeReferenceId="newPassword" PartnerClaimType="password"/>
  <PersistedClaim ClaimTypeReferenceId="displayName" DefaultValue="unknown" />
  <PersistedClaim ClaimTypeReferenceId="passwordPolicies" DefaultValue="DisablePasswordExpiration" />
  <PersistedClaim ClaimTypeReferenceId="givenName" />
  <PersistedClaim ClaimTypeReferenceId="surname" />
</PersistedClaims>

Please let me know if you have any questions and I can help you further.

If this answer helps you please mark "Accept Answer" so other users can reference it.

Thank you,

James

Steve Bi 0

Persisted Claim is used. No problem save the user's option when they signup first time:

      <ClaimType Id="extension_communicationChoice">
        <DisplayName></DisplayName>
        <DataType>string</DataType>
        <UserInputType>CheckboxMultiSelect</UserInputType>
        <Restriction>
          <Enumeration Text=" I would like to receive communications about updates .." Value="AgreeToCommunicationYes" SelectByDefault="false" />
        </Restriction>
      </ClaimType>

TP:
        <TechnicalProfile Id="SelfAsserted-ProfileUpdate">
          <DisplayName>User ID signup</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.profileupdate</Item>
          </Metadata>
          <IncludeInSso>false</IncludeInSso>
          <InputClaims>
            <InputClaim ClaimTypeReferenceId="extension_profile_description" DefaultValue="" />
            <InputClaim ClaimTypeReferenceId="userPrincipalName" />

            <!-- Optional claims. These claims are collected from the user and can be modified. Any claim added here should be updated in the
                 ValidationTechnicalProfile referenced below so it can be written to directory after being updated by the user, i.e. AAD-UserWriteProfileUsingObjectId. -->
            <InputClaim ClaimTypeReferenceId="givenName"/>
            <InputClaim ClaimTypeReferenceId="surname"/>
            <InputClaim ClaimTypeReferenceId="country"/>
            <InputClaim ClaimTypeReferenceId="postalCode"/>
            <InputClaim ClaimTypeReferenceId="extension_communicationChoice" DefaultValue="AgreeToCommunicationNo" />
          </InputClaims>
          <OutputClaims>
            <!-- Required claims -->
            <OutputClaim ClaimTypeReferenceId="executed-SelfAsserted-Input" DefaultValue="true" />
            <OutputClaim ClaimTypeReferenceId="extension_profile_description" />
            <OutputClaim ClaimTypeReferenceId="givenName"  Required="true" />
            <OutputClaim ClaimTypeReferenceId="surname"  Required="true" />
            <OutputClaim ClaimTypeReferenceId="country"  Required="true" />
            <OutputClaim ClaimTypeReferenceId="postalCode" />
            <OutputClaim ClaimTypeReferenceId="extension_communicationChoice"/>
          </OutputClaims>
          <ValidationTechnicalProfiles>
            <ValidationTechnicalProfile ReferenceId="AAD-UserWriteProfileUsingObjectId" />
          </ValidationTechnicalProfiles>
        </TechnicalProfile>


the persist TP
        <TechnicalProfile Id="AAD-UserWriteProfileUsingObjectId">
          <Metadata>
            <Item Key="Operation">Write</Item>
            <Item Key="RaiseErrorIfClaimsPrincipalAlreadyExists">false</Item>
            <Item Key="RaiseErrorIfClaimsPrincipalDoesNotExist">true</Item>
          </Metadata>
          <IncludeInSso>false</IncludeInSso>
          <InputClaims>
            <InputClaim ClaimTypeReferenceId="objectId" Required="true" />
          </InputClaims>
          <PersistedClaims>
            <!-- Required claims -->
            <PersistedClaim ClaimTypeReferenceId="objectId" />

            <!-- Optional claims -->
            <PersistedClaim ClaimTypeReferenceId="givenName" />
            <PersistedClaim ClaimTypeReferenceId="surname" />
            <PersistedClaim ClaimTypeReferenceId="country" />
            <PersistedClaim ClaimTypeReferenceId="postalCode" />
            <PersistedClaim ClaimTypeReferenceId="extension_communicationChoice" DefaultValue="AgreeToCommunicationNo" />
          </PersistedClaims>
          <IncludeTechnicalProfile ReferenceId="AAD-Common" />
        </TechnicalProfile>
      </TechnicalProfiles>


The problem happens if user change their mind, want to uncheck the "
extension_communicationChoice" as no, the value can't be captured 

Thanks!

Steve Bi 0 Reputation points

2024-05-20T21:49:03.1833333+00:00

Share via

with b2c custom policy, capture checkbox state during profile editing

1 answer

Your answer