Re: [I] Superset API return 401 Access Denied: Invalid Credential even when using admin account [superset]
EuphoriaCelestial commented on issue #27961: URL: https://github.com/apache/superset/issues/27961#issuecomment-2048797879 > A few diagnostic questions: > > 1. Does it work via the UI, or is it throwing errors there, too? > > 2. Are _all_ POST endpoints not working, or is it just this one? 1. No, the UI is not working to, throwing the same error 2. I am working with db create api and login only, so I can't test other endpoint, but login is also POST and its fine > I'm not sure, but it looks like maybe the db connection is throwing the error, not the API... this makes me ask the two questions above, and I wonder if the URI indeed contains the right credentials for the db. You mean the credentials and DB for login Superset? or credential and DB for the connection that I am creating? -- 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: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
Re: [I] Superset API return 401 Access Denied: Invalid Credential even when using admin account [superset]
rusackas commented on issue #27961: URL: https://github.com/apache/superset/issues/27961#issuecomment-2047874630 A few diagnostic questions: 1) Does it work via the UI, or is it throwing errors there, too? 2) Are _all_ POST endpoints not working, or is it just this one? I'm not sure, but it looks like maybe the db connection is throwing the error, not the API... this makes me ask the two questions above, and I wonder if the URI indeed contains the right credentials for the db. -- 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: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
[I] Superset API return 401 Access Denied: Invalid Credential even when using admin account [superset]
EuphoriaCelestial opened a new issue, #27961: URL: https://github.com/apache/superset/issues/27961 ### Bug description Hi, as the title said, I am using Superset API to do things like create DB connection, create users, ... The login, get csrf token endpoints is fine, and I am also be able to call GET endpoints like get all DB connection, get all users, ... using the access token and csrf token of successful admin login But when using POST endpoints, like create DB connection, it return 401 error ### How to reproduce the bug 1. Call login and get csrf token endpoint to get access token and csrf token for later use 2. Call /api/v1/database/ endpoint, method POST, to create new connection 3. Get error ### Screenshots/recordings  ### Superset version 3.1.2 ### Python version 3.9 ### Node version 16 ### Browser Firefox ### Additional context _No response_ ### Checklist - [X] I have searched Superset docs and Slack and didn't find a solution to my problem. - [X] I have searched the GitHub issue tracker and didn't find a similar bug report. - [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- 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: notifications-unsubscr...@superset.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
