Trouble configuring the delegated admin extension

Help
1

I have followed the tutorial and am able to log into my delegated administration extension website. However when the site makes the api call to get the user list, there is a 403 forbidden error. I’m not able to find any way to troubleshoot this error.

I am running Delegated Administration Dashboard 2.6

The response is “{“error”:“ForbiddenError”,“message”:“Forbidden! Sorry, you have no permissions to do this.”}”

The access token that is being sent to the API does not include any role or scope data, not sure if this is an issue.

Here is a stack trace from the server log

4:45:03 PM: 2018-04-02T23:45:03.830Z - error: ForbiddenError: Forbidden! Sorry, you have no permissions to do this.
at /data/io/0b2d0aab-2c3d-4852-a6ed-afc4189b66d0/webtask.js:1:224191
at Layer.handle [as handle_request] (/data/_verquire/express/4.14.0/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/data/_verquire/express/4.14.0/node_modules/express/lib/router/index.js:312:13)
at /data/_verquire/express/4.14.0/node_modules/express/lib/router/index.js:280:7
at Function.process_params (/data/_verquire/express/4.14.0/node_modules/express/lib/router/index.js:330:12)
at next (/data/_verquire/express/4.14.0/node_modules/express/lib/router/index.js:271:10)
at e.exports (/data/io/0b2d0aab-2c3d-4852-a6ed-afc4189b66d0/webtask.js:1:224071)
at Layer.handle [as handle_request] (/data/_verquire/express/4.14.0/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/data/_verquire/express/4.14.0/node_modules/express/lib/router/index.js:312:13)
at /data/_verquire/express/4.14.0/node_modules/express/lib/router/index.js:280:7
at Function.process_params (/data/_verquire/express/4.14.0/node_modules/express/lib/router/index.js:330:12)
at next (/data/_verquire/express/4.14.0/node_modules/express/lib/router/index.js:271:10)
at t (/data/io/0b2d0aab-2c3d-4852-a6ed-afc4189b66d0/webtask.js:1:269732)
at /data/io/0b2d0aab-2c3d-4852-a6ed-afc4189b66d0/webtask.js:1:230353
at /data/io/0b2d0aab-2c3d-4852-a6ed-afc4189b66d0/webtask.js:1:255406
at /data/io/0b2d0aab-2c3d-4852-a6ed-afc4189b66d0/webtask.js:1:255515
at u (/data/io/0b2d0aab-2c3d-4852-a6ed-afc4189b66d0/webtask.js:1:250420)
at nextTickCallbackWith0Args (node.js:489:9)
at process._tickDomainCallback (node.js:459:13)

2

:wave: @jlines is this happening on a new tenant you created?

3

It is, I just created a free tenant to act as my development environment.

4

Hi @kimcodes. Should I open a ticket for this issue? Do you think it has something to do with the new tenant I created?

5

@jlines terribly sorry about the delay getting back to you. And you are logging in as the user who has the delegated admin role applied? Is this on a OIDC Complaint client ?

6

Correct, I am logging in a user that has the delegated admin role applied using the Authorization Extension.

The client I am using is the one that is a part of the Delegation extension, which the docs say is not OIDC compliant, and I have disabled OIDC compliance in the client options.

7

Hey there!

Sorry for the delay in response. We’re doing our best in providing you with best developer support experience out there, but sometimes there are too many questions to handle. Sorry for the inconvenience!

Do you still require further assistance from us?