If I fully integrated Janrain or Oneall Social Login , what obstacles could migrate into my own system?
For example, many developers use the social plugin Janrains (and many others) because they do not have time to execute all the code to provide their own solution or because of its quick and convenient.
However, somewhere in the future, perhaps when the developer has more time, he can write his own solution using, for example, the OpenID selector and the openid library (for example, his own stackoverflow solution). In addition, Janrain and Oneall become expensive, it’s good that your first few thousand users, but after a sudden increase in user registration, it becomes incredibly expensive (especially if you use only a social login and not other social functions)
I see that in my facebook application the website URL (for example, one), I pass the FB application: http://myapp.api.oneall.com/ ', which processes all the verification and binds the account and then redirects the URL callback address of my websites.
However, if I replaced Oneall with my own solution (the site URL will change), what happens? Then authentication will become invalid, no? and the user will have to accept permissions again? How do I achieve a successful migration?
I hope I explained it quite well. This may be trivial, but some clarification would be greatly appreciated. I want to make sure that I am not tied to Oneall or Janrain.
source share