> On 16 Nov 2016, at 14:50, Cory Benfield <[email protected]> wrote: > > >> On 16 Nov 2016, at 11:51, Roland Hedberg <[email protected]> wrote: >> >> The bottom line is of course that it would benefit the community to have a >> high quality OAuth2/OIDC implementation within easy reach. > > I think the core question you need to answer for this proposal is: why is > “pip install oic” not easy-enough reach?
Basically, I think it’s a matter of visibility. If someone tells you you have to add OIDC RP capabilities to your service what do you do. If the needed batteries are already included in Python it’s easy, it’s there. If it isn’t then the best case scenario is that you find all the implementations there is and based on objective evaluations (like the OIDF standards compliant tests) chose the ‘best’ one. Is that the most common scenario ? I doubt it. The OIDF will publish information about their preferred set of libraries but I still think there will be a substantial portion of coders we won’t reach. If you have any idea about how we could reach more coders I’m all ears. — Roland _______________________________________________ Python-ideas mailing list [email protected] https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
