Note that there are some explanatory texts on larger screens.

plurals
  1. POdesire2learn valence get users call giving 403 not authorized error
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COAre you able to make the call with another, more privileged, user context? I'd recommend starting with a no-privileges user and building up the perms until you can make the call you want, and then looking for diffs between your no-privs user role and the one you're really wanting to use, but you can try working backwards, too. Look for diffs from a more privileged role and starting taking away towards the problematic one... If you're having issues with this call with all users, then maybe connect to D2L support and send us a trace?
      singulars
    2. COThe user that I'm using has almost all the privileges. As per the "Investigating Roles Permissions" topic in Valence webpage, I see that even a non privileged user who's enrolled at the root level can make this call. I guess I should report this to d2l help desk. May be it's a configuration issue.
      singulars
    3. COIt would be useful to know exactly what the 403 you're getting back looks like. The 403 can result from various kinds of errors, at various layers in the webservice, so seeing a captured request/response traffic session would be very useful. I'm assuming that using the same code to sign API requests you're making _other_ calls that do work?
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload