I believe you can set up certificates. You then store the certificates in a Java keyring file, and tell Java about the keyring at startup. Now, when you make an HTTP connection, the HTTP library automatically uses the certificates. You don't need any custom code in the http client.
(I think this is how it works, anyway.) On Thu, Apr 26, 2012 at 3:01 PM, Michael Della Bitta <michael.della.bi...@appinions.com> wrote: > Really? Is that in a .properties file somewhere, or would I have to do > it in code? > > I was sort of hoping I'd be able to add the credentials to the URL in > the shards field, but looking at the source, that won't fly. While we're > on the topic, it might be nice to be able to specify the connection > scheme, too (e.g. for HTTPS). > > I'd be willing to make a patch if there's a decision on the way this > should work. > > Thanks, > > Michael > > On Thu, 2012-04-26 at 17:55 -0400, Mark Miller wrote: >> On Apr 26, 2012, at 5:25 PM, Michael Della Bitta wrote: >> >> > Hi, >> > >> > I'm wondering if there's any way to use container-based HTTP auth and >> > Distributed Search configured in the SearchHandler that I haven't >> > discovered aside from writing my own shard handler implementation. >> > >> > Thanks, >> > >> > Michael >> > >> >> >> I think there is an ugly global way to support this by setting some global >> properties for HttpClient. I can't remember clearly offhand though. >> >> We should add explicit support for this I think - just like we have for >> replication. >> >> - Mark Miller >> lucidimagination.com >> >> >> >> >> >> >> >> >> >> >> > > -- Lance Norskog goks...@gmail.com
