Manage connected third-party applications using Three-Legged OAuth 2.0

Blackboard Learn 9.1 Q4 2017
Blackboard Learn SaaS Continuous Delivery v3300.0.0| Release to Production 13 October 2017
Ultra Experience, Original Experience

Starting with this release, Blackboard Learn provides support for three-legged OAuth (3LO) 2.0 authorization. Developers can create applications using REST APIs that act on a user's behalf in a more secure way. When authorized using 3LO, applications can act on behalf of a user and therefore are restricted to the parts of Learn for which that user has permissions to access.

When users work in a third-party tool, the application may ask your permission to operate within Learn on your behalf. This process allows the application to submit assignments or tasks the user has completed to Blackboard Learn. Similar to syncing social media applications, the integration allows learning platforms to work together. Once a user allows access, they can manage the authorization from the Tools panel.

Previously, such applications could only work with Learn using generic credentials. Generic credentials had all permissions needed for the application, regardless of individual user's access levels. This method also didn't provide the ability to track individual user activities. Now, Learn supports either method: the use of generic credentials or user-specific credentials and permissions.

More on Three-legged OAuth and Blackboard Learn