What's a commonly accepted way of implementing SSO using a third party OAuth provider?I have a server with user resources associated with server's user ID, the user ID also has a Facebook user ID associated. Would it be a good approach to authenticate a client to the server if the login was redirected to, say, Facebook where it would return an OAuth token and the token is then shared with the client?Suppose SSL is implemented, the OAuth token would then act in the same way as a session cookie that gives permission to user resources on the server. The same user an different client can then reauthenticate with Facebook which would return the same Facebook ID, which gives access to the same user's resources and a different OAuth token which expires independently and removing the app on Facebook can callback the server with a deauthenticate request to keep things synchronised. Is this a good policy to use? Is it safe against attacks like session sidejacking, cross site reference etc?
Should OAuth token be shared to implement SSO?
security;ssl;oauth