Fwd: FYI: Devstack oAuth+SSO for Ecommerce

[Robert Raposa]

Hello Braden.

On master branch, you’ll need an ecommerce-sso oauth application with a scope for user_id. See below for automated instructions.

I forgot to copy edx-code on the original email, so I’m doing that now.

Begin forwarded message:

From: Robert Raposa <rra...@edx.org>
Date: March 29, 2019 at 4:04:26 
Subject: FYI: Devstack oAuth+SSO for Ecommerce

TL;DR Previously provisioned devstacks will need an admin record added in order for Ecommerce SSO to continue to work.  (This will also be true for credentials if and when it upgrades its auth-backends to 2.0.0+.)

Longer:

If you need Ecommerce SSO to work in devstack with the latest ecommerce code, and you provisioned your devstack before today, you will need a new record added in admin.

With an admin account (e.g. e...@example.com) in devstack:

1. Get the latest edx-platform code.  It has a required bug fix.
2. Log in to the devstack lms with an admin account (e.g. e...@example.com)
• http://localhost:18000/
  
3. Go to http://localhost:18000/admin/oauth_dispatch/applicationaccess/
4. Add a new Application Access.
• Choose the ecommerce-sso application.
• If you don't see ecommerce-sso, get the latest code from edx-platform and devstack, and then run devstack's provision-ecommerce.sh. You can skip the rest of these instructions.
• Add the scope user_id.
• Save
5. Success (we hope)!  SSO should now work again.

FYI: The latest version of the backend EdxOAuth2 for oAuth+SSO now requires the user_id in order to work.

If you have any questions or concerns, please let me know. Thank you.

--

Robert Raposa

edX | Software Architect  | rra...@edx.org  

141 Portland Street, 9th floor

Cambridge, MA 02139

http://www.edx.org