We're testing out SSO via multipass and we've run into a bit of a hiccup when users change their email address inside our app. It seems that it what accounts that get implicitly created by Tender are keyed off of - and when a user changes their email address on file, they can no longer access private threads they were part of [or be associated with a previous identity].
What is the best way to mitigate this issue - something having a UID for a user so that it isn't their username [which could change] or their email [which could change] be the critical piece of identifying email to Tender?

#1 Posted by rick on 20 Nov, 2009 04:38 PM
Ah, it's probably creating a whole new user when that happens. As an immediate work-around:
The challenge with what you propose is sending a user ID to your app. I don't think the API supports Multipass yet, but I'll add that really soon in light of this problem. Your app would have to make some multipass request to the API:
From there, you could get the user ID and pass that with future multipass login tokens on the main site.
You can get the user ID right now by making an API request like this:
Thanks for the feedback!
#2 Posted by rick on 08 Jan, 2010 04:26 AM
Jeff: we solved this issue once and for all. First, the Multipass docs were expanded with the new attributes that we support. One of them is indeed a
unique_idfeature so your users can change their addresses without getting a new Tender profile. There's a specific Multipass migration document for helping with a transition from existing Multipass accounts.rick closed this discussion on 08 Jan, 2010 04:26 AM.