xueyun0512 opened a new issue, #40678:
URL: https://github.com/apache/superset/issues/40678

   ### Bug description
   
   Hello, 
   I want to connect to Apache Solr. However, since I have configured Solr to 
use Kerberos, I can't connect to the Solr server directly (as solr-sqlalchemy 
does not support Kerberos authentication protocol). 
   Therefore, I have set an proxy in front of Solr. I'm using Knox Gateway.  
   
   When I tried the following URi 
   
solr://username:[email protected]:443/europe-italy/team-tiramisu/solr/cheese_collection
   
   Where:
   443: port 
   europe-italy/team-tiramisu: knox gateway topology
   cheese_collection: my Solr collection name 
   
   I got the error:
   ERROR: Expecting value: line 1 column 1 (char 0)
   
   Can you help me please? 
   
   In this case, what is the easiest solution? 
   1) Change the source code solr-sqlalchemy to support Kerberos?
   2) Change the source code solr-sqlalchemy to use Knox Gateway ? 
   
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.11
   
   ### Node version
   
   I don't know
   
   ### Browser
   
   Chrome
   
   ### 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.
   - [x] 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: [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]

Reply via email to