Skip to content

Implement Janrain Capture and Janrain Engage auth provider #2398

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
AndrewLane opened this issue Jul 26, 2016 · 5 comments · Fixed by #8549
Closed

Implement Janrain Capture and Janrain Engage auth provider #2398

AndrewLane opened this issue Jul 26, 2016 · 5 comments · Fixed by #8549
Labels
state:released Released as stable version state:released-alpha Released as alpha version state:released-beta Released as beta version

Comments

@AndrewLane
Copy link
Contributor

AndrewLane commented Jul 26, 2016 •
edited
Loading

Implement Janrain Capture and Janrain Engage auth provider

This would be an addition to parse server to allow for authentication using Janrain. Janrain provides an Engage product as well as a Capture product, so there will be separate auth providers for each. It would be similar to Twitter, Facebook, etc. which are already implemented.

I will be submitting a PR but I wanted to submit this issue first for any necessary discussion.
@AndrewLane AndrewLane changed the title Implement Janrain OAuth provider Implement Janrain Capture and Janrain Engage OAuth provider Jul 28, 2016
@AndrewLane AndrewLane changed the title Implement Janrain Capture and Janrain Engage OAuth provider Implement Janrain Capture and Janrain Engage auth provider Jul 28, 2016
@AndrewLane AndrewLane mentioned this issue Aug 1, 2016
Merged
@AndrewLane
Copy link
Contributor Author

Pull request added: #2436

@snyk-bot snyk-bot mentioned this issue Feb 26, 2023
Closed
@parseplatformorg parseplatformorg mentioned this issue May 21, 2023
Merged
@snyk-bot snyk-bot mentioned this issue May 22, 2023
Closed
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 6.1.0-alpha.13

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label May 25, 2023
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 6.3.0-beta.1

@parseplatformorg parseplatformorg added the state:released-beta Released as beta version label Jun 10, 2023
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 6.3.0-alpha.1

@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 6.3.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label Sep 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
state:released Released as stable version state:released-alpha Released as alpha version state:released-beta Released as beta version
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

refactor: Upgrade redis from 4.0.6 to 4.6.6 parse-community/parse-server
2 participants
@AndrewLane @parseplatformorg