You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have some code that's been originally written for could code for OAuth2 providers, it needs a refactor as it was using an external object to store the login informations.
I have the basic implementations for instagram, meetup, linkedin, as well as the iOS side.
Twitter login could also be added in that, but since it's OAuth 1.1 that's a totally different game.
@gfosco is it something you'd like to see integrated soon or you prefer to wait for stabilization?
I investigated already, I believe I'll start with OAuth2 flows, in an extensible way.
Quick architectural question, are the ParseServer options exposed in the RestWrite?
@nlutsenko the PR is open with meetup, instagram, and linked in. I didn't realize initially that the full oAuth flow is not provided by parse-server itself so adding twitter would be just another validator.
Quick question for you all (since you implemented this). We have two Twitter apps (one our iOS clients are using and one that our Android clients are using). How do we specify two sets of keys in index.js?
Activity
gfosco commentedon Feb 4, 2016
That would be great, don't think we need to wait. Looks like most of the work is in RestWrite.js.
flovilmart commentedon Feb 4, 2016
I investigated already, I believe I'll start with OAuth2 flows, in an extensible way.
Quick architectural question, are the ParseServer options exposed in the RestWrite?
flovilmart commentedon Feb 4, 2016
@gfosco I could also refactor the Facebook login around this new OAuth provider as they will share 99% of the code, what do you think?
nlutsenko commentedon Feb 5, 2016
That's an awesome idea!
And the SDKs are already built in a way that can support this.
One of the potential ways for building this could be via custom cloud functions or similar piece, so anyone can bring in their own validation.
Look into how Facebook is hooked on right now - all of this could be similar, where we would store the data in _User.
flovilmart commentedon Feb 5, 2016
@nlutsenko the PR is open with meetup, instagram, and linked in. I didn't realize initially that the full oAuth flow is not provided by parse-server itself so adding twitter would be just another validator.
We could also support custom validator through:
This could be added before tomorrow
gfosco commentedon Feb 16, 2016
This will be landing in #247. 🎆
sprabs commentedon Jul 12, 2016
Quick question for you all (since you implemented this). We have two Twitter apps (one our iOS clients are using and one that our Android clients are using). How do we specify two sets of keys in index.js?
#2254
flovilmart commentedon Jul 12, 2016
It isn't supported yet