3 ms·
I received an invite to this service today and just checked it out - this is not correct. You have to generate your own keys for each service, then store them
by tehwebguy 13y ago
I received an invite to this service today and just checked it out - this is not correct.
You have to generate your own keys for each service, then store them with OAuth.io. This doesn't mean they can't access your users' data, just that there isn't one "master key" that could shut everyone down.
- btilly 13y agoThanks for the correction. In that case, I fail to see the value add that they claim to provide.
- nadiac 13y agoI feel it is made for fast Oauth integration. We use 4 oauth providers into one of our app, and it took us really 4 full days to implement them without bug. We are not Oauth experts but it was really boring and IMO useless implementation time. Also I'm personaly making a client-side app on a Github page and it seems that with oauth.io I could make a serverless Facebook/Twitter authenticated app.
- sondh 13y agoFacebook and Twitter OAuth implementations both support response_type=token for serverless authorization.