Skip to content
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

Consider using velruse to support multiple authentication providers #509

Closed
almet opened this issue Mar 15, 2016 · 7 comments
Closed

Consider using velruse to support multiple authentication providers #509

almet opened this issue Mar 15, 2016 · 7 comments
Labels
question scope:authentication

Comments

@almet
Copy link
Member

almet commented Mar 15, 2016

There is a pyramid project that could be of some use here, named Velruse. We should have a deeper look into that, as it seems to integrate with a bunch of third party autentication providers.
@almet
Copy link
Member Author

almet commented Mar 15, 2016

Velruse can be used either as a pyramid plugin or as a separate service.

@leplatrem
Copy link
Contributor

Velruse has not received any commit for 3 years.

@Natim
Copy link
Member

Natim commented Mar 15, 2016

Velruse has not received any commit for 3 years.

Does it means that we should not use it?
The developers behind it are from Mozilla and the project is well tested so it should be usable IMHO.

@almet
Copy link
Member Author

almet commented Mar 15, 2016

What do you think @bbangert ?

@bbangert
Copy link

If velruse hasn't needed a commit in three years, then it hasn't gotten one. :)

Now, there does seem to be 15 PR's, and some issues. We could fix that up fairly easily, merge the ones that work, and get a new release out. If the desire is to support multiple auth's, that'd be far easier than re-implementing velruse.

@almet
Copy link
Member Author

almet commented Mar 16, 2016

That sounds like a reasonable thing to do, yes!

lavish205 pushed a commit to lavish205/kinto that referenced this issue Jun 20, 2016
@leplatrem
Add pool with max_backlog option (fixes Kinto#509)
3f70254 
This code from imported from Mozilla Services Sync.
See mozilla-services/server-syncstorage@f93ca85

*Note: Cliquet is licensed under Apache and Sync is under MPL*
lavish205 pushed a commit to lavish205/kinto that referenced this issue Jun 20, 2016
@leplatrem
Merge pull request Kinto#569 from mozilla-services/509-sqla-queue-max…
b2a0875 
…-backlog

Add pool with max_backlog option (fixes Kinto#509)
@leplatrem leplatrem mentioned this issue Jun 15, 2017
Closed
@leplatrem
Copy link
Contributor

We went for OpenID Connect support only. It's enough for now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question scope:authentication
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@almet @bbangert @Natim @leplatrem