OAuth 2.0 Client Credentials Flow Support for Brightspace (M2M)
Is there any support for OAuth 2.0 flows other than Authorization Code Grant (preferably Client Credentials flow)? I'm needing support for fully headless automation, and the need for a user to log in with a browser in order to get an initial authorization code doesn't make sense for a fully automated environment. Private Key JWT authentication would work, or perhaps Client Secret authentication. Any current support or upcoming support?
Answers
-
Hi Brett, in this case, I would recommend connecting with your institution's IT Help Desk for some support with this. If you need any assistance locating that contact information, please let me know and I will send it via DM.
-
I'm asking about support for Brightspace. All I see is documentation about the Authorization Code Grant in regard to OAuth 2.0.
-
Have you looked at the new Service Account for OATH apps ? I am trying to figure out how to get it going but I am not sure we have the infrastructure.
Question, when specifying the JWKS URL, can you just use https://{institution}.brightspace.com/d2l/.well-known/jwks ? I'm not exactly sure where we might have an authentication server other than the D2L authentication.If that will work, what, then is meant by the information in next steps for developers:
- Configure the external authorization server to sign a JSON Web Token (JWT) with the private key that corresponds to the public key in the JWKS URL.
- Implement the OAuth 2.0 Client Credentials flow with Private Key JWT to exchange the signed JWT for an access token from Brightspace.
This is from
