Skip to content
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

apache-druid-0.13.0-incubating router /druid/router/v1/brokers #6786

Closed
panqingcui opened this issue Dec 29, 2018 · 4 comments · Fixed by #8026
Closed

apache-druid-0.13.0-incubating router /druid/router/v1/brokers #6786

panqingcui opened this issue Dec 29, 2018 · 4 comments · Fixed by #8026
Labels
Milestone

Comments

@panqingcui
Copy link

ERROR PreResponseAuthorizationCheckFilter:106 - Request did not have an authorization check performed.: {class=org.apache.druid.server.security.PreResponseAuthorizationCheckFilter, uri=/druid/router/v1/brokers, method=GET, remoteAddr=172.19.104.129, remoteHost=172.19.104.129}

@srggrs
Copy link

srggrs commented Mar 13, 2019

I have a similar error when introspec a global caches lookup (Druid 0.13.0):

2019-03-13T02:05:12,997 ERROR [qtp1043822951-119] org.apache.druid.server.security.PreResponseAuthorizationCheckFilter - Request did not have an authorization check performed.: {class=org.apache.druid.server.se$ urity.PreResponseAuthorizationCheckFilter, uri=/druid/v1/lookups/introspect/portfolio_uuid, method=GET, remoteAddr=127.0.0.1, remoteHost=127.0.0.1} 2019-03-13T02:05:12,998 WARN [qtp1043822951-119] org.eclipse.jetty.server.HttpChannel - /druid/v1/lookups/introspect/portfolio_uuid org.apache.druid.java.util.common.ISE: Request did not have an authorization check performed.

funny thing if I issue the request with:

curl -X GET http://localhost:8082/druid/v1/lookups/introspect/mylookup
curl is able to retrieve part of the lookup map, but when I use the same endpoint in a Python requests, it failed.

@egor-ryashin
Copy link
Contributor

@panqingcui could you post here Druid version and router configuration?

@stale
Copy link

stale bot commented Jun 20, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 20, 2019
@stale
Copy link

stale bot commented Jul 4, 2019

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants