This article helps clarify the process that occurs in Password Manager when a user’s mobile number is changed in AD and its effect in Starling 2FA.
1) PM or Starling have no mechanisms or agents for checking and updating users mobiles (when changed in AD);
2) When a Password Manager/Starling 2FA registered user engages with a PM’s workflow (containing a step to authenticate with Starling 2FA), the Product fetches the mobile number and email of the corresponding user from AD (attributes) and sends those to Starling 2FA;
3) If the number has changed in AD, Starling will check for a valid subscription and re-registers the user automatically;
4) A Starling Admin should then be able then to delete the obsolete/duplicate user objects if necessary.