get Forbidden statuscode on User Attributes api
{{BrightspaceDomain}}/d2l/api/lp/{{lpversion}}/attributes/users/
/d2l/api/lp/1.42/attributes/users/143002
With IdKey authenticaion, this api returns Fordidden
Is there any configuration causing this issue?
Best Answer
-
So to have the user Attributes you require to have Manager Dashboard enabled and this is not a core product it is a paid for additional product.
The Attributes themselves would normally be configured by a D2L Integration consultant when the product is installed as far as I am aware.
I would suggest you check if you have the Manager Dashboard product or contact your D2L CSM or if your Institution has a TAM contact them.
Answers
-
If you take a look at the documentation for that API call, a "403 Forbidden" status code means that the caller does not have permission to view user attributes. Are you making this request from a browser that you have an active Brightspace session?
-
I have tried this tool
the major question is how to configure the permission to view user attributes.
-
As per the comment above can you check permission and authentication as I tried it with the api test tool and had no issues.
-
The Brightspace user on behalf of whom the API call is made (the calling user context) must have permissions to see the user attributes for the user identified in the API call. Typically if the user context's user can do some functionality in the Brightspace UI, then API calls made on their behalf providing equivalent functionality should be allowed. You should ensure that user context's user can see user attributes for another user in the Brightspace UI; if their enrollment role doesn't give them sufficient privileges to do so, then they shouldn't be abllowed to do this via the APIs either.
-
Thanks for your reply, I have done some research. User Attributes permission needs to be configured by Manager Dashboard or Learning Groups Organization on the navbar. But I cannot find Manager Dashboard on the navbar
I logged in as DevCoP Admin
-
Ok so I think then that the main issue here is that the User attributes are not setup and configured on that DevCop test site, which is why you are getting the 403 error.
Do you have access to your institution site that has the attributes setup and configured, if so I would suggest trying the command against that site. -
Right now I have a super administrator access to my client instituion, but still has no access to user attributes. Could you give me the detailed instruction on how to configure it.
