For SSO login definitely you need to have your user_id and some basic details which allow you to connect to FB or google


provider: "it will be either FB or Google or anything in future"
token: "This token we receive from FB and Google. In case of FB it
expires after 3 months or so where as it does not expire for google
as per my knowledge" 
token_expired:" As In FB token expires after a time so you can have
this flag in place if you need to refresh it after that duration"
user_id: "This is your User id: 
uniqueid: "This is the Unique ID which you will get from FB and Google.
That helps to identify your user in FB/Google"


These are the minimum fields you can add and these will even help you to scale your app. In the sense if you want to pull or push data from google and FB at that time Access_token and unique_id will help you.

Also incase you want to see some publish source then you can see some of the code on github e.g.
django-social-auth

For some details you can refer google documentation and Google OAuth2

Hope this will help.

Database table structure for storing SSO information for FB or Google+
In the Day of the Doctor the War Doctor sets a program running on his screwdriver which 11's then has then completed.

However 10 burnt out his Screwdriver in "Smith and Jones" working on the MRI machine and 11 lost his screwdriver in the "11th Hour"

If that's the case how can the program still be running?
