Google Identity - Delete account - oauth-2.0

So we're evaluating creating a Google Social Login for our software. We're wondering what happens if someone stops using Google/Twitter/Facebook and deletes their account there? Is there sort of account recovery process or best practice recovery method?
We really appreciate your help!

Related

Social login concept and best practice

I have started building a website on Laravel and I wanted to include social Login to my site.
I have a basic understanding of how this works. I used Socialite and Google API and followed the documentation and setup a login route to google and was able to get a response with token and other details.
This is where I am stuck. I wan't to build a robust user system. I need help in understanding the best concept for Social login.
For example,
when a user logs in from google, do I need to save the token. Do I need to create an entry in the database and save as a user or should I just load the user information every time from what is returned by the API.
Also, what is the difference between social login and sing up with social login?
Ultimately, I would like to build a site with user profiles and I would like to get as much information from API's as possible and setup the user system in efficient way.
Any help is much appreciated

How to migrate to a token based login approach- iOS application?

First of all, I know that this is a very broad question and may not look appropriate. But, I just want to get a heads-up on this item so that I get move in the right direction.
We have an existing iOS application where we depend on backend RESTful web services. We have username/password based authentication in place. The user has to enter the credentials every time he/she wants to login.
Now, we are moving to Touch ID based biometric authentication and hence the idea is to implement a token based authentication mechanism so that we don't have to store the user password in keychain (which is secured but not completely on a rooted device).
I know that there are multiple ways to implement token based authentication. If someone can help me with any good library or changes to do server and client side, it would be of great help. Thanks.
Please let me know if you need any clarifications.

DEVELOPER_TOKEN_NOT_APPROVED Adwords

Good day guys,
Please, I am working on a project that requires setting up Google Adwords account in order to use the API. I am using the Python Client Library. I am getting a DEVELOPER_TOKEN_NOT_APPROVED error when I run my test application.
After a lot of research on the issue, I figured maybe I didn't set up the production and test accounts properly which I am still struggling with. I really hope you can put me through the process as I am running against time.
Looking forward to your help
Thank you very much.
You need Developer Token from production account, but until approval is pending you need authorize API call only for test AdWords account. You need two different Google accounts. You must get Refresh Token after login to your another Google account for testing purpose.
More info: https://developers.google.com/adwords/api/docs/guides/accounts-overview#test_accounts

IOS user registration

I want to create a user login system that will eventually handle a lot of users and information linked to the users. I've looked a lot into core data but can someone tell me from experience how I should handle my data? Should I use core data? Also I'm programming in swift.
Singing in/up with an email is important for almost every app that requires a social interaction. In the past, developers often used Parse (backend-provider) as to implement a login system. But, Parse is closing down soon. So, here we have another solution, as someone mentioned, "Firebase". Firebase allows you to quickly create a login system integrated with email, Facebook, Github, Google, you name it. You are also able to store user information such as photos and personal information using Firebase's core feature known as 'Real time database' and "Storage". Here is a quick introduction for you to learn more about Firebase!
Introduction to Firebase Authentication
https://www.youtube.com/watch?v=8sGY55yxicA
Introduction to Firebase Database
https://www.youtube.com/watch?v=U5aeM5dvUpA
Login Tutorial by Jared
https://www.youtube.com/watch?v=8sRUhzgJhcY
There is a learning curve, but let me know if you are stuck,
read the documentation and "get started guideline"
https://firebase.google.com/docs/ios/setup
If you find this information useful, I would appreciate your thumbs up!

How can I maintain user credentials (django server) in a way that bypasses the login page on an iOS app even after turning the phone off?

I've been told to use Oauth2.0, but I don't understand what I am to do with it on either side.
I would specifically like to achieve the persistent login that Facebook and Twitter maintain in their respective iOS apps.
PLEASE give me a specific answer (and hopefully an example too!)
I know that this may be achieve with Oauth2.0, but I have been unable to find an example as to how (even after extensive research- if I could find the answer I wouldn't be asking the question here.)
Thank you in advance!
-John

Resources