sudeshnasengupta opened a new issue, #13148:
URL: https://github.com/apache/pinot/issues/13148
When extending org.apache.pinot.broker.broker.AccessControlFactory to have
Pinot v. 1.1.0 Broker talk to a Keycloak server for authenticating all Broker
POST "query/sql" API calls, and configuring the associated, local Broker
distribution to use the custom factory via the Broker configuration property
"pinot.broker.access.control.class", the only way the same local Pinot v.1.1.0
distribution works is if that customization is part of the "pinot-broker"
module from Pinot's code base. However, if the uber JAR containing the
customization and all its dependencies is dropped into the same distribution's
"lib" or "plugins" folder, the Broker HTTP server encounters a response 500,
leading to the following "Grizzly 2.4.4" error response body:
<html><head><title>Grizzly 2.4.4</title><style><!--div.header
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#003300;font-size:22px;-moz-border-radius-topleft:
10px;border-top-left-radius: 10px;-moz-border-radius-topright: 10px;bo
rder-top-right-radius: 10px;padding-left: 5px}div.body
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:#FFFFCC;font-size:16px;padding-top:10px;padding-bottom:10px;padding-left:10px}div.footer
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#666633;font-size:14px;-moz-border-radius-bottomleft:
10px;border-bottom-left-radius: 10px;-moz-border-radius-bottomright:
10px;border-bottom-right-radius: 10px;padding-left: 5px}BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;}B
{font-family:Tahoma,Arial,sans-serif;color:black;}A {color : black;}HR {color :
#999966;}--></style> </head><body><div class="header">Request failed.</div><div
class="body">Request failed.</div><div class="footer">Grizzly
2.4.4</div></body></html>.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
