Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

Implement OAuth support #21

Open
cpq opened this issue Oct 24, 2014 · 6 comments
Open

Implement OAuth support #21

cpq opened this issue Oct 24, 2014 · 6 comments
Assignees
@cpq
Labels
feature

Comments

@cpq
Copy link
Member

cpq commented Oct 24, 2014

No description provided.

@cpq cpq added the feature label Oct 24, 2014
@cpq cpq added this to the Release 3.0 milestone Oct 24, 2014
@cpq cpq added the p2 label Oct 30, 2014
@cpq cpq assigned mkmik Nov 1, 2014
@cpq cpq assigned alashkin and unassigned mkmik Feb 26, 2015
@alashkin
Copy link
Contributor

Are we talking about OAuth 2.0 only, or we need both 1.0 and 2.0?

@cpq
Copy link
Member Author

cpq commented Mar 23, 2015

I think we should stick to 2.0

@alashkin
Copy link
Contributor

Agree.

@alashkin
Copy link
Contributor

And we want to have implementation of all roles described in its RFC?

@cpq
Copy link
Member Author

cpq commented Mar 23, 2015

We want minimal functionality that would allow to authorize through e.g. github and google.

@cpq cpq added p1 and removed p2 labels Mar 24, 2015
@cpq cpq removed this from the Release 3.0 milestone Apr 20, 2015
@cpq cpq removed the p1 label Aug 17, 2015
@alashkin alashkin assigned cpq and unassigned alashkin Mar 21, 2017
@alashkin
Copy link
Contributor

Shall we close this issue?

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@cpq cpq

Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mkmik @cpq @alashkin