Hi joderose -
When you are using sso, your system becomes the system of record. The Lithium application will respect any change coming from that system. If you do not send information in the sso token, the user will be able to set that info in the community and have it 'stick'. One solution might be to have the user opt out of sharing their basic profile info with the community and then adjust what is sent in their sso token. That would need to be done on your side though (wherever the sso cookie is originating from).
Kaela
Thanks, Kaela. I think what I'm looking for then is an admin option to allow the user to override SSO-provided values. In other words, if a user has set a value, allow that to have a higher precedence than the SSO value.
