Going forward we will only support django-oauth-toolkit. Additionally, we will move away from OpenID Connect in favor of OAuth 2.0 + JWT access tokens. We have had a proxy in production for quite sometime that provides the ability to issue JWT access tokens: https://github.com/edx/edx-platform/blob/master/openedx/core/djangoapps/oauth_dispatch/views.py#L89-L90.
The exact timeframe for fully implementing these changes across all services/APIs is still to be decided. If you're planning to create a new API or service, use OAuth 2.0 + JWT. If you're attempting to integrate an existing service (e.g. ecommerce), please follow the appropriate guides (which still reference django-oauth2-provider). Clinton Blackburn, Tech Lead edX E-Commerce Engineering On Monday, December 5, 2016 at 9:51:26 AM UTC-5, f pichlu wrote: > > Which one of django-oidc-provider and edx-oauth2-provider is better,for > using a Django application in edx-platform? > -- You received this message because you are subscribed to the Google Groups "General Open edX discussion" group. To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/5d3e3564-9f47-4806-9e3e-691fbbac9385%40googlegroups.com.
