Best Of

Hi Richard,

Currently all applications using the Valence APIs require explicit user consent to make API calls and therefore can only use the three legged workflow requiring a Brightspace user to log in.

However we do support a “service user pattern” for application integrations that are intended to be administrative scripts, middleware development and so forth:

1. Create a service user/role combination to associate with your application that has the permissions the application/script needs.
2. Login manually as this user to go through the workflow to be able to provision the application/script with credentials; the credentials need to be stored securely for/with your application.
3. For OAuth2: the credentials in step 2 will come with a short-lived access token and a longer-lived refresh token (one use); the app will then need to be designed to, on a regular basis, use the refresh token workflow to ask for a new access token and refresh token combo — unlike the step 2 request, the refresh token workflow can be done directly with Auth service and needs no user in between. The initial access token request is three legged and returns an access token and one-use refresh token; the refresh token workflow is two legged and trades that refresh token directly in for another access token and one-use refresh token.

This is also covered in the following resource, https://community.brightspace.com/s/article/How-to-get-started-with-OAuth-2-0 related resources are also available from the linked resource.

Hope that helps!