GitHub user geovanasullivan added a comment to the discussion: 403 Forbidden on 
embedded dashboard in production (worked fine in test), missing can read on 
CurrentUserRestApi permission?

Thanks for the earlier guidance, that was really helpful in confirming the root 
cause. @dosu

Update: I confirmed that can read on CurrentUserRestApi did not exist in the 
database for this 6.0.0 install at all (not just hidden in the role editor UI). 
I created the missing permission_view manually via the Security REST API (POST 
/api/v1/security/permissions-resources/ with permission_id for can_read and 
view_menu_id for CurrentUserRestApi), then assigned it to the Public role 
through the normal UI.

However, the 403 error persists, and I've now isolated it to a different stage 
of the flow:

In our local/test environment, the guest token is generated successfully and 
the embedded dashboard loads without issues.
In production, the backend call to generate the guest token isn't succeeding at 
all, it's failing before a token is even returned, using the exact same 
SUPERSET_URL, SUPERSET_USER, and SUPERSET_PASSWORD values as local.

Since both environments point to the same Superset instance and use identical 
credentials, this looks like it may be network-related (e.g., the production 
server's outbound IP not being allowed to reach the Superset instance, or some 
proxy/firewall layer in front of it), rather than a permissions issue this time.

Has anyone run into guest token generation failing specifically from a 
production server while working fine locally against the same Superset 
instance? Any pointers on what to check on the network/infrastructure side 
would be appreciated.

GitHub link: 
https://github.com/apache/superset/discussions/42547#discussioncomment-17827374

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to