Is there a way to keep the user’s “Preferences > Alternate Phone” number in sync with an authoritative source attribute?
From what I can tell, this is populated on initial identity creation using the “Personal Phone (phone)” identity attribute value, but I’m not even entirely sure that is true. An authoritative agg doesn’t even appear to update this identity attribute, which seems very odd considering it’s the authoritative source.
I’ve also seen the phone number populated on the IdentityNow source account personalPhone attribute, but that only happens if a user went to preferences and saved their general settings. It doesn’t even keep the same e.164 format. There is obviously no way to sync to the IdentityNow source account itself.
The idea is to have the end users to go to our HR platform ONLY to set their phone number, agg it, then sync it to their alternate phone preferences. In the current configuration, they would have to update with HR AND also update in SP preferences. Our largest population of frontline workers really have little need to sign in to SailPoint, but we need their phone number in sync for password mgmt reasons. It’s going to cause confusion and an unnecessary amount of calls to helpdesk support.
This really doesn’t make sense to me and documentation doesn’t really spell this out in my opinion.
hi Jonathan, your observasion on personal phone under preference is correct. If you update the value it will update on identity attribute Personal Phone and also on IdentityNow source account attribute personalPhone. If you have mapping in your identity profile with Auth source for identity attribute Alternative Phone (phone) then this would be that value it shows on user Preference. So if you agg it from HR source you should be able to see it in SP.
Thank you for the response! What you described is how I would expect this to work. However, it doesn’t work this way.
I even retested after your response to 100% confirm it does not. I updated my number in our HR system and aggregated. I see the change reflected on my HR source account, but my personal phone identity attribute remains the old number, also preferences number did not change. This was after I processed my identity to rule out that requirement.
I reconfirmed the mapping in our identity profile as well.
I’m not sure if this is a bug or intended behavior from SailPoint. If intended, it would be nice to have the option to change that behavior.
Really I was hoping someone has found a workaround in some way.
@colin_mckibben Any chance you would be able to confirm functionality of alternate phone? Does it sound like something in our tenant configuration needs addressed or should alternate phone/preferences update with an authoritative aggregation?
I am not sure why it is not working Jonathan. Yes may be a support ticket should be created to SailPoint and let them check. But I will wait for Colin to respond. He may have some more insights