RE: Programmatic Basic Auth on CloudSolrClient
Hi Tomas, Tried your suggestion. But last suggestion (directly passing the httpclient) resilts in NonRepeatableRequestException. And using full step, also didn’t recognize the auth. Anything I should look for? Thanks, Subhajit From: Tomás Fernández Löbbe<mailto:tomasflo...@gmail.com> Sent: 05 March 2021 04:23 AM To: solr-user@lucene.apache.org<mailto:solr-user@lucene.apache.org> Subject: Re: Programmatic Basic Auth on CloudSolrClient Ah, right, now I remember that something like this was possible with the "http1" version of the clients, which is why I created the Jira issues for the http2 ones. Maybe you can even skip the "LBHttpSolrClient" step, I believe you can just pass the HttpClient to the CloudSolrClient? you will have to make sure to close all the clients that are created externally after done, since the Solr client won't in this case. On Thu, Mar 4, 2021 at 1:22 PM Mark H. Wood wrote: > On Wed, Mar 03, 2021 at 10:34:50AM -0800, Tomás Fernández Löbbe wrote: > > As far as I know the current OOTB options are system properties or > > per-request (which would allow you to use different per collection, but > > probably not ideal if you do different types of requests from different > > parts of your code). A workaround (which I've used in the past) is to > have > > a custom client that overrides and sets the credentials in the "request" > > method (you can put whatever logic there to identify which credentials to > > use). I recently created > https://issues.apache.org/jira/browse/SOLR-15154 > > and https://issues.apache.org/jira/browse/SOLR-15155 to try to address > this > > issue in future releases. > > I have not tried it, but could you not: > > 1. set up an HttpClient with an appropriate CredentialsProvider; > 2. pass it to HttpSolrClient.Builder.withHttpClient(); > 2. pass that Builder to > LBHttpSolrClient.Builder.withHttpSolrClientBuilder(); > 3. pass *that* Builder to > CloudSolrClient.Builder.withLBHttpSolrClientBuilder(); > > Now you have control of the CredentialsProvider and can have it return > whatever credentials you wish, so long as you still have a reference > to it. > > > On Wed, Mar 3, 2021 at 5:42 AM Subhajit Das > wrote: > > > > > > > > Hi There, > > > > > > Is there any way to programmatically set basic authentication > credential > > > on CloudSolrClient? > > > > > > The only documentation available is to use system property. This is not > > > useful if two collection required two separate set of credentials and > they > > > are parallelly accessed. > > > Thanks in advance. > > > > > -- > Mark H. Wood > Lead Technology Analyst > > University Library > Indiana University - Purdue University Indianapolis > 755 W. Michigan Street > Indianapolis, IN 46202 > 317-274-0749 > www.ulib.iupui.edu<http://www.ulib.iupui.edu> >
Re: Programmatic Basic Auth on CloudSolrClient
Ah, right, now I remember that something like this was possible with the "http1" version of the clients, which is why I created the Jira issues for the http2 ones. Maybe you can even skip the "LBHttpSolrClient" step, I believe you can just pass the HttpClient to the CloudSolrClient? you will have to make sure to close all the clients that are created externally after done, since the Solr client won't in this case. On Thu, Mar 4, 2021 at 1:22 PM Mark H. Wood wrote: > On Wed, Mar 03, 2021 at 10:34:50AM -0800, Tomás Fernández Löbbe wrote: > > As far as I know the current OOTB options are system properties or > > per-request (which would allow you to use different per collection, but > > probably not ideal if you do different types of requests from different > > parts of your code). A workaround (which I've used in the past) is to > have > > a custom client that overrides and sets the credentials in the "request" > > method (you can put whatever logic there to identify which credentials to > > use). I recently created > https://issues.apache.org/jira/browse/SOLR-15154 > > and https://issues.apache.org/jira/browse/SOLR-15155 to try to address > this > > issue in future releases. > > I have not tried it, but could you not: > > 1. set up an HttpClient with an appropriate CredentialsProvider; > 2. pass it to HttpSolrClient.Builder.withHttpClient(); > 2. pass that Builder to > LBHttpSolrClient.Builder.withHttpSolrClientBuilder(); > 3. pass *that* Builder to > CloudSolrClient.Builder.withLBHttpSolrClientBuilder(); > > Now you have control of the CredentialsProvider and can have it return > whatever credentials you wish, so long as you still have a reference > to it. > > > On Wed, Mar 3, 2021 at 5:42 AM Subhajit Das > wrote: > > > > > > > > Hi There, > > > > > > Is there any way to programmatically set basic authentication > credential > > > on CloudSolrClient? > > > > > > The only documentation available is to use system property. This is not > > > useful if two collection required two separate set of credentials and > they > > > are parallelly accessed. > > > Thanks in advance. > > > > > -- > Mark H. Wood > Lead Technology Analyst > > University Library > Indiana University - Purdue University Indianapolis > 755 W. Michigan Street > Indianapolis, IN 46202 > 317-274-0749 > www.ulib.iupui.edu >
Re: Programmatic Basic Auth on CloudSolrClient
On Wed, Mar 03, 2021 at 10:34:50AM -0800, Tomás Fernández Löbbe wrote: > As far as I know the current OOTB options are system properties or > per-request (which would allow you to use different per collection, but > probably not ideal if you do different types of requests from different > parts of your code). A workaround (which I've used in the past) is to have > a custom client that overrides and sets the credentials in the "request" > method (you can put whatever logic there to identify which credentials to > use). I recently created https://issues.apache.org/jira/browse/SOLR-15154 > and https://issues.apache.org/jira/browse/SOLR-15155 to try to address this > issue in future releases. I have not tried it, but could you not: 1. set up an HttpClient with an appropriate CredentialsProvider; 2. pass it to HttpSolrClient.Builder.withHttpClient(); 2. pass that Builder to LBHttpSolrClient.Builder.withHttpSolrClientBuilder(); 3. pass *that* Builder to CloudSolrClient.Builder.withLBHttpSolrClientBuilder(); Now you have control of the CredentialsProvider and can have it return whatever credentials you wish, so long as you still have a reference to it. > On Wed, Mar 3, 2021 at 5:42 AM Subhajit Das wrote: > > > > > Hi There, > > > > Is there any way to programmatically set basic authentication credential > > on CloudSolrClient? > > > > The only documentation available is to use system property. This is not > > useful if two collection required two separate set of credentials and they > > are parallelly accessed. > > Thanks in advance. > > -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu signature.asc Description: PGP signature
RE: Programmatic Basic Auth on CloudSolrClient
Thanks. This would be very helpful.
From: Tomás Fernández Löbbe<mailto:tomasflo...@gmail.com>
Sent: 04 March 2021 12:32 AM
To: solr-user@lucene.apache.org<mailto:solr-user@lucene.apache.org>
Subject: Re: Programmatic Basic Auth on CloudSolrClient
Maybe something like this (I omitted a lot of things you'll have to do,
like passing zk or the list of hosts):
static class CustomCloudSolrClient extends CloudSolrClient {
protected CustomCloudSolrClient(CustomCloudSolrClientBuilder builder) {
super(builder);
}
@Override
public NamedList request(SolrRequest request, String
collection) throws SolrServerException, IOException {
// your logic here to figure out which credentials to use...
String user = "user";
String pass = "pass";
request.setBasicAuthCredentials(user, pass);
return super.request(request, collection);
}
}
static class CustomCloudSolrClientBuilder extends CloudSolrClient.Builder {
@Override
public CloudSolrClient build() {
return new CustomCloudSolrClient(this);
}
}
public static void main(String[] args) {
CloudSolrClient c = new CustomCloudSolrClientBuilder().build();
...
}
Do consider that "request" method is called per request, make sure whatever
logic you have there is not super expensive.
On Wed, Mar 3, 2021 at 10:48 AM Subhajit Das
wrote:
> Hi Thomas,
>
> Thanks. Can you please also share a sample of code to configure the client
> with your workaround?
>
> From: Tomás Fernández Löbbe<mailto:tomasflo...@gmail.com>
> Sent: 04 March 2021 12:05 AM
> To: solr-user@lucene.apache.org<mailto:solr-user@lucene.apache.org>
> Subject: Re: Programmatic Basic Auth on CloudSolrClient
>
> As far as I know the current OOTB options are system properties or
> per-request (which would allow you to use different per collection, but
> probably not ideal if you do different types of requests from different
> parts of your code). A workaround (which I've used in the past) is to have
> a custom client that overrides and sets the credentials in the "request"
> method (you can put whatever logic there to identify which credentials to
> use). I recently created https://issues.apache.org/jira/browse/SOLR-15154
> and https://issues.apache.org/jira/browse/SOLR-15155 to try to address
> this
> issue in future releases.
>
> On Wed, Mar 3, 2021 at 5:42 AM Subhajit Das
> wrote:
>
> >
> > Hi There,
> >
> > Is there any way to programmatically set basic authentication credential
> > on CloudSolrClient?
> >
> > The only documentation available is to use system property. This is not
> > useful if two collection required two separate set of credentials and
> they
> > are parallelly accessed.
> > Thanks in advance.
> >
>
>
Re: Programmatic Basic Auth on CloudSolrClient
Maybe something like this (I omitted a lot of things you'll have to do,
like passing zk or the list of hosts):
static class CustomCloudSolrClient extends CloudSolrClient {
protected CustomCloudSolrClient(CustomCloudSolrClientBuilder builder) {
super(builder);
}
@Override
public NamedList request(SolrRequest request, String
collection) throws SolrServerException, IOException {
// your logic here to figure out which credentials to use...
String user = "user";
String pass = "pass";
request.setBasicAuthCredentials(user, pass);
return super.request(request, collection);
}
}
static class CustomCloudSolrClientBuilder extends CloudSolrClient.Builder {
@Override
public CloudSolrClient build() {
return new CustomCloudSolrClient(this);
}
}
public static void main(String[] args) {
CloudSolrClient c = new CustomCloudSolrClientBuilder().build();
...
}
Do consider that "request" method is called per request, make sure whatever
logic you have there is not super expensive.
On Wed, Mar 3, 2021 at 10:48 AM Subhajit Das
wrote:
> Hi Thomas,
>
> Thanks. Can you please also share a sample of code to configure the client
> with your workaround?
>
> From: Tomás Fernández Löbbe<mailto:tomasflo...@gmail.com>
> Sent: 04 March 2021 12:05 AM
> To: solr-user@lucene.apache.org<mailto:solr-user@lucene.apache.org>
> Subject: Re: Programmatic Basic Auth on CloudSolrClient
>
> As far as I know the current OOTB options are system properties or
> per-request (which would allow you to use different per collection, but
> probably not ideal if you do different types of requests from different
> parts of your code). A workaround (which I've used in the past) is to have
> a custom client that overrides and sets the credentials in the "request"
> method (you can put whatever logic there to identify which credentials to
> use). I recently created https://issues.apache.org/jira/browse/SOLR-15154
> and https://issues.apache.org/jira/browse/SOLR-15155 to try to address
> this
> issue in future releases.
>
> On Wed, Mar 3, 2021 at 5:42 AM Subhajit Das
> wrote:
>
> >
> > Hi There,
> >
> > Is there any way to programmatically set basic authentication credential
> > on CloudSolrClient?
> >
> > The only documentation available is to use system property. This is not
> > useful if two collection required two separate set of credentials and
> they
> > are parallelly accessed.
> > Thanks in advance.
> >
>
>
RE: Programmatic Basic Auth on CloudSolrClient
Hi Thomas, Thanks. Can you please also share a sample of code to configure the client with your workaround? From: Tomás Fernández Löbbe<mailto:tomasflo...@gmail.com> Sent: 04 March 2021 12:05 AM To: solr-user@lucene.apache.org<mailto:solr-user@lucene.apache.org> Subject: Re: Programmatic Basic Auth on CloudSolrClient As far as I know the current OOTB options are system properties or per-request (which would allow you to use different per collection, but probably not ideal if you do different types of requests from different parts of your code). A workaround (which I've used in the past) is to have a custom client that overrides and sets the credentials in the "request" method (you can put whatever logic there to identify which credentials to use). I recently created https://issues.apache.org/jira/browse/SOLR-15154 and https://issues.apache.org/jira/browse/SOLR-15155 to try to address this issue in future releases. On Wed, Mar 3, 2021 at 5:42 AM Subhajit Das wrote: > > Hi There, > > Is there any way to programmatically set basic authentication credential > on CloudSolrClient? > > The only documentation available is to use system property. This is not > useful if two collection required two separate set of credentials and they > are parallelly accessed. > Thanks in advance. >
Re: Programmatic Basic Auth on CloudSolrClient
As far as I know the current OOTB options are system properties or per-request (which would allow you to use different per collection, but probably not ideal if you do different types of requests from different parts of your code). A workaround (which I've used in the past) is to have a custom client that overrides and sets the credentials in the "request" method (you can put whatever logic there to identify which credentials to use). I recently created https://issues.apache.org/jira/browse/SOLR-15154 and https://issues.apache.org/jira/browse/SOLR-15155 to try to address this issue in future releases. On Wed, Mar 3, 2021 at 5:42 AM Subhajit Das wrote: > > Hi There, > > Is there any way to programmatically set basic authentication credential > on CloudSolrClient? > > The only documentation available is to use system property. This is not > useful if two collection required two separate set of credentials and they > are parallelly accessed. > Thanks in advance. >
