Framework integrations
What are the modules we want to have ready with 1.0?
- [ ] Ruby/Rails
- [x] Ruby/Sinatra
- [x] Python
- [ ] Python/Django
- [ ] Python/Flask
- [x] Node.js
- [x] PHP
- [ ] Wordpress
- [x] Serendipity
Let's complete the list
Edit: Are there OIDC libraries that work with LA? If yes, we should list them as well.
- Python/Django
- Python/Flask
django-allauth is the library of choice for django authentication and they won't have an issue accepting PRs.
I marked ruby/sinatra as done, because https://github.com/onli/sinatra-browserid/tree/letsauth exists now and worked fine so far.
Is there someone that would be motivated to implement a module for another language/framewok? It would be great to distribute the work, and to have some more integrations ready when the core is up and running.
I'm planning to use Portier in my Rust web app which uses Iron etc. in the backend and Polymer/Web Components in the front end. Not sure how large the demand for a Rust relying party is in general, but I'm certainly interested. Right now my auth is password based but I want to switch to portier as soon as possible.
For the log: There is a guide on how to use Pythons asyncio on https://www.viktorroytman.com/blog/2017/01/23/using-portier-with-pythons-asyncio/
I've updated the original comment, checked off Node.js and PHP with links to libraries.
I did investigate generic OAuth2 and OIDC libraries for Node.js and PHP, but I'm not sure what reasons I had for not using them. I believe they just seemed complicated. In the PHP case, OAuth2 libraries sometimes implement just the access token flow, and not id tokens as used by OIDC.
I'm thinking of deploying Portier on Pastery, so I'd be writing a Django library in the process. It looks good enough to use in production already, I think, especially since Pastery just uses email-based auth anyway.
I looked at the PHP integration, am I right to assume what is done with redis there could be done with the $wpdb mysql backend for wordpress as well? They say it powers 27% of the web, could really give this a boost and a lot of users who report potential issues.
@nextgenthemes Yes, that would be absolutely possible, and great for the project. There are Wordpress browserid plugins that could serve as base, the php client by @stephank is working great and can be extended to work with the Wordpress backend, and the browserid-ported-to-portier plugin for the php blogengine Serendipity could also serve as example.