7frank commented on issue #25890:
URL: https://github.com/apache/superset/issues/25890#issuecomment-3789960953
@bronz3beard @rusackas
> Deleting the Public user on a fresh instance was what worked for me
partially too.
- I was trying to set up a Superset MCP neither was able to list dashboards
while connected.
- I tried the Cookie&CSRF Token attempts that others have highlighted. Which
which listed **1 Dashboard**.
- I tried the Bearer Token approach which listed **0 Dashboards** which was
in line what i saw from my mcp servers.
> Only after I deleted the Public Role i was able to get the same Response
with Bearer Token that i have gotten earlier with Cookie
This looks like something is up with the AuthZ Logic. Logging in as `Admin`
Role, is influenced by the `Public` Role
For reference:
```
claude mcp add --transport stdio superset \
-e SUPERSET_BASE_URL=https://... \
-e SUPERSET_USERNAME=admin \
-e SUPERSET_PASSWORD=admin \
-- npx -y superset-mcp
claude mcp add --transport stdio superset \
-e SUPERSET_API_URL=https://... \
-e SUPERSET_USERNAME=admin \
-e SUPERSET_PASSWORD=admin \
-- docker run -i --rm \
-e SUPERSET_API_URL \
-e SUPERSET_USERNAME \
-e SUPERSET_PASSWORD \
pondered/superset-mcp:latest
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
