OAuth2 Per-Application Scopes

[douglashall]

No description provided.

[edx-status-bot]

Your PR has finished running tests. The following contexts failed:

• jenkins/python
• jenkins/a11y
• jenkins/bokchoy

[nasthagiri]

These changes need to be included in the v1 of the Grades API - and not part of v0.

[mettursathish]

Nice, Catch!

[mettursathish]

Thank @douglashall! As promised, we were working on migration script(sql) and authorize.html changes. The python migration code looks good, you can incorporate authorize.html code which displays the organization filter(if applicable) from the below commit edx@fdc9e0e. Also merged as part of this PR https://github.com/edx/edx-platform/pull/18117

[nasthagiri]

@mettursathish Should that commit include the authorize.html file?

[mettursathish]

@douglashall, @nasthagiri
Instead of making changes to the authorize.html; the approach was to append the scope description. If OAuth client_Id is associated with the organization filter; then append organization name with scope description at the suffix. By this approach, we have little more flexibility of the description which is getting displayed in authorize.html. Also, profile scope, email scope is generic to the open edX instance and not specific to any organization. So, the idea of appending the scope description makes it easier. Attaching the screenshot for reference.

[nasthagiri]

This was closed in favor of https://github.com/edx/edx-platform/pull/18408