Is there functionality to invalidate other session tickets if the user logins again?
This would be particularly useful when users play cross platform on multiple devices. We don't want one client overwriting UserData from another client.
Is there functionality to invalidate other session tickets if the user logins again?
This would be particularly useful when users play cross platform on multiple devices. We don't want one client overwriting UserData from another client.
Not currently. The initial design of the service was specifically to allow for multiple device scenarios, so a session ticket provided by the service is valid for 24 hours currently. We will be updating later this quarter with an updated model which will provide for true session tokens, which will allow titles to enforce the only one sign in design. We'll be posting more info on this update when it is complete.
1 Person is following this question.
