Brightspace dynamic registration

Forum:

Learning Tools Interoperability Public Forum

Brightspace dynamic registration

Submitted by David Lippman on Thu, 03-Feb-2022 14:54.

I'm trying to implement dynamic registration, but am not sure how to handle Brightspace, for which the OAuth2 audience (used during token request) is not the same as the token URL, like it is for every other LMS.

The dynamic registration spec doesn't have a specific property for this listed in 2.1 or 3.6 of the spec, so I was wondering if anyone knows and could share how Brightspace returns the OAuth2 audience as part of the dynamic registration workflow.

Thanks!

Nevermind

Nevermind. I just wasn't looking hard enough. It's there in 2.1, the authorization_server parameter.

Submitted by David Lippman on Thu, 2022-02-03 19:02

Nevermind

Nevermind. I just wasn't looking hard enough. It's there in 2.1, the authorization_server parameter.

Submitted by David Lippman on Thu, 2022-02-03 19:02

The names 1EdTech^® and IMS Global Learning Consortium^®, the 1EdTech logos, Better Learning From Better Learning Technology^®, TrustEd Apps™, 1EdTech TrustEd Apps™, Learning Tools Interoperability^®, LTI^®, IMS LTI^®, IMS Learning Tools Interoperability^®, OneRoster^®, Caliper Analytics^®, Question & Test Interoperability (QTI)^®, QTI^®, Common Cartridge^®, Competencies and Academic Standards Exchange^®, CASE^®, Competencies and Academic Standards Exchange (CASE)^®, Accessible Portable Item Protocol (APIP)^®, AccessForAll^®, Badge Connect^®, Comprehensive Learner Record Standard™, and CLR Standard™ are trademarks of 1EdTech Consortium, Inc. in the United States and/or other countries. All other trademarks and registered trademarks are the properties of their respective owners.

For information on the 1EdTech trademark usage policy, see our trademark policy page.