title: Laravel 5.3 - Social login doubts
body: <p>I am developing a mobile app and currently depending on JWT to maintain the statelessness of the API. The API is consumed by mobile and web devices. The users will use their email and password to register. </p>
  
  <p>I am assigned to implement social login option in this API. I would like to clear my following doubts.</p>
  
  <p>1) When Social Login is used, how can I generate a token [like JWT] which will be stored at the client's end? This token is supposed to send with all subsequent requests after login.</p>
  
  <p>2) In case social platforms are not providing/sharing email address [which is one of our primary keys], what all information shall I store?</p>