1

Currently I only find documentation that allows me to change my email / username / phone number, but nothing talks about adding a user attribute as an authentication entity for the login.

Jose Alvarez
  • 13
  • 4

1 Answers1

2

Write the new identifier to signInNames.whatever, exactly like the “change identifier” samples work. They just overwrite an existing value, if one didn’t exist, it just gets created automatically.

You can’t add an identifier to /any/ attribute, it has to go into signInNames attribute, as that is uniquely constrained.

Jas Suri - MSFT
  • 10,605
  • 2
  • 10
  • 20
  • Apparently it only works for the signUp, but in reality I need to authenticate by the document number – Jose Alvarez Dec 27 '21 at 04:57
  • You need to write the doc number into signInNames.docNumber. At sign-in, you don’t need to make any changes other than switching the operating mode of the sign in technical profile to username and using the appropriate regex restriction for the signInName field. https://learn.microsoft.com/en-gb/azure/active-directory-b2c/self-asserted-technical-profile#metadata – Jas Suri - MSFT Dec 27 '21 at 11:43
  • thank you!!!!!!! I needed to ensure that it could not be done otherwise – Jose Alvarez Dec 27 '21 at 14:41
  • @JasSuri-MSFT When you create something like `signInNames.whatever` are you limited to 64 characters in length (like with username)? I am hoping for a way to get ~300 chars. – Dessus Sep 10 '22 at 11:20
  • 1
    No, the limit is much higher if you use .foo. Around 500char. – Jas Suri - MSFT Sep 10 '22 at 14:58