Problems calling Superset Api with authentication via oauth provider #26107
Replies: 2 comments 4 replies
-
We have found a solution. |
Beta Was this translation helpful? Give feedback.
2 replies
-
Hi,
This user can authenticate on Superset bypassing oauth provider. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi to all,
we have integrated Superset 2.1.0 in our application, using KeyCloak as identity provider.
The integration works correctly, so we can access to Superset functions from our application.
Now we would like to call SuperSet Api from an external standalone application, but we have some authentication problems.
In particular we generate a JWT token with a curl like the following, where client_id, client_secret and url are the same configured in superset_config.py of our superset installation:
and obtain an HTTP 200 response with a Bearer access_token .
Then we set this token in the Authorization header of a Superset rest call and obtain HTTP 401 with message : "The client application my_app has forbidden access".
Are these steps correct or there is another way to proceed?
What could be the problem?
In attachment my superset_config.py
Thanks,
Tania
superset_config.txt
Beta Was this translation helpful? Give feedback.
All reactions