-
Notifications
You must be signed in to change notification settings - Fork 14.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CUSTOM_SECURITY_MANAGER not working in 0.34.0rc1 #8062
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
Hi @ericandrewmeadows , We had the same issue as explained in that StackOverflow question although we are using a different openId connect provider called IdentityServer4. We, therefore, did a custom security manager that does the integration by extending the superset security manager. I would be happy to provide my approach if need be. It involved a little bit of code and understanding of the workings of openId connect(built on top of OAuth2) |
Can you please provide:
This could be a FAB related issue, feel free to open an issue there so we can narrow it down |
IMO, the 0.34 release has a good deal of bug fixes/improvements that merit releasing 0.34 rather than 0.33. As 0.34 will (hopefully) become the first official ASF Superset release, there will for sure be many bugs that surface as people try it out. Rest assured committers (myself included) will give reported issues high priority to make sure that bugs are ironed out of the 0.34 branch (along with master) as quickly as possible. |
Custom SM:
|
Sorry - accidentally opened & closed.
The server logs actually do not give any issues, but with the custom SM, it is not ending up reaching |
@villebro - my main item is that v0.33.0rc1 -> v0.34.0rc1 broke custom security, and is a large issue. I am also beginning to make commits and help this as well, I am just waiting on some people to comment on the features I am contributing on. |
i need to create an authentication with jwt identity to access api inside it |
Any updates here? |
Have you tried to disable |
@dpgaspar - no go on that. There is something in the routes which is circumventing the security manager with v0.34.0rc (1, and 2). Relevant settings from above, tested just now:
|
The symptom is very direct, now that I was able to trace it out even more: |
Testing a proposed fix for this and will put up a PR. |
App routing is broken in the latest release with respect to Custom Security Manager. Please deprecate this release.
Expected results
When attempting to access the root url for Superset, this should redirect to the login page if the user is not logged in. This redirect is failing to work when
AUTH_TYPE = AUTH_OID
Actual results
The app routes to
/superset/welcome
Screenshots
If applicable, add screenshots to help explain your problem.
How to reproduce the bug
Environment
(please complete the following information):
npm -v
Checklist
Make sure these boxes are checked before submitting your issue - thank you!
Additional context
This works perfectly fine on
0.33.0rc1
, so I have had to downgrade. Because of this issue, where the routing is not correct, I believe this issue should be resolved and 0.34.0rc1 should be pulled.The text was updated successfully, but these errors were encountered: