The scopes you register your app with only express the scopes that your app could ask for when requesting a token. You must still specify the scopes you want when actually making a token request; even in that case, in theory, the Brightspace Auth service could only provide a token with a subset of the scopes that were requested, so you may want to verify you got the scopes you asked for and/or be able to copy gracefully with not having all the scopes you asked for (I say in theory, because even though we're within the bounds of OAuth2 to behave that way with token scopes, I'm not sure the Brightspace Auth service would actually do that: give you a token with only a subset of the requested scopes). Please verify that: - when making a token request, you're asking for the scopes you expect to need with that token - if you can, the token you've received actually has the scopes you expect it to have
Thanks Viktor! but i am doing exactly that, asking for the scops i need and checking that i have received them. but still getting the same error message. it sounds very weird to me.
That does sound weird, and I'm not sure I have much to add; you could try requesting the more specific users:userdata:update scope, but that should not matter. What API version are you using here (that also should not matter, though, as the users:userdata:update scope should apply to all versions of that API action)?
users:userdata:update
version
I tried all that but it didn't work out.
If you can share the URL you are using for your auth request it might help diagnose the issue. You could remove the client id & redirect uri if you don't want to share those. Alternatively, you could just share the scope parameter from the auth url to see if there's an issue there.
I believe that in the original commenter's situation, they were not calling the API route correctly. Can you confirm what the actual URL is that you're calling here? If you do feel you're calling the correct API route as documented, you can try opening a support case.
My error was that I was accidentally using POST instead of PUT (for doing an update instead of a create). Using PUT corrected the issue.
Thanks.
Connect with our Known and Fixed Issue information to learn about improvements made to Brightspace.
Connect with leaders in pedagogy, accessibility, learning experience design and more
The Accessibility category serves as a single point of access to three avenues in Brightspace Community leading to the Accessibility Academy, Accessibility Library and Accessibility Discussions. These avenues offer courses and articles about accessibility to enhance accessibility knowledge and a group of accessibility enthusiasts to stay connected with.
Have questions about how to use Community? Stay tuned with updates, feedback opportunities and more for the Community here!
Connect with and ask questions on how to best use the Brightspace Product to transform the way your users learn!
Connect with product experts to learn more about tools frequently used by Brightspace Developers such as APIs and integrations!
Want to learn more about Brightspace Partners and Integrations? This is the place to be!
Stay up to date with product updates and announcements in this category.
Connect with our release information to learn about monthly improvements and updates to Brightspace.
Learn more about all the upskilling opportunities with courses and resources offered via the Brightspace Learning Center, Brightspace Guided Training and other training opportunities!
