This might be of interest to operators and other Open edX instances that will migrate from Ironwood to Juniper.
Any OAuth Applications/Clients registered in the LMS that are using the old Django-OAuth-Provider will need to be migrated to Django-OAuth-Toolkit. These applications include your Open edX Mobile Apps (iOS, Android) as well as your Open edX services (e-commerce, Insights, Credentials, etc.) TBD . Need to include step-by-step information for this migration.
Does edX have instructions on how to do it? Thus far I can do it manually by looking at the database or tables in Django Admin for Ironwood and recreate the entries in the appropriate tables in Django Admin, but I’m afraid some people will not be able to do so.
Luckily for us the migrations did not remove the table oauth2_client where the previous information is stored. On the other hand, this table is no longer displayed in Django Admin in Juniper.
We need to find a way to automated the DOP to DOT upgrade because some Open edX instances or operators will not have the technical expertise to do it manually. It might also cause some downtime for instances relying on these services like ecommerce, discovery or insights to give a few examples.
Since edX must have gone through this process internally for edx.org, is there any documentation available that can be shared with the community?
Thanks for any information or instructions you can provide.