Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

95
Views
Sign in strategy with OAuth ( Google / Apple sign In )

in one of my projects I have implemented a login / registration with the OAuth from Google and Apple.

Now when I request a login I get back something like the following tokens:

  • AccessToken
  • ID-Token
  • RefreshToken

My strategy is to send the ID token to my own backend to check if it is valid. I create the user in my own database with new internal credentials. I don't need and don't store the other tokens at all. The users are automatically logged in using the new credentials.

The login of the client is now always done automatically by the own credentials.

Does this strategy bring any disadvantages?
Should I still save the other tokens?
If so for what benefit?

If the user logs out, I simply repeat the process afterwards and recognize from the ID sent along in the ID token that he is already registered.

Thank you guys for your opinion and help.

about 4 years ago · Juan Pablo Isaza
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!