Thanks, Josh

Our code that works with LabKey 14.3 and HttpClient 3.x is the following:

GetMethod get = new GetMethod( urlString );
	labkeyConnection.executeMethod( get );
	String fileContents = get.getResponseBodyAsString();

where urlString is the URL as a String, labkeyConnection is a org.labkey.remoteapi.Connection, properly authenticated via username and password.

I think I figured out most of how to re-write this using the new API - except for authentication. Here is what I have so far (without error/exception handling):

CloseableHttpClient httpClient = labkeyConnection.getHttpClient( 60 );
	HttpGet get = new HttpGet( urlString );
	CloseableHttpResponse response = httpClient.execute( get );
	HttpEntity entity = response.getEntity();
	String fileContents = EntityUtils.toString( httpEntity );

When I execute this, the fileContents appears to be the login page, rather the file I want. I started looking at the docs for how to do authentication with the new HttpClient APIs here: https://hc.apache.org/httpcomponents-client-ga/tutorial/html/authentication.html and it seems like rather a lot of code (CredentialsProvider, AuthCache, BasicScheme, HttpClientContext, etc.), and I'm wondering why I have to re-authenticate, if I'm using the CloseableHttpClient object gotten from the LabKey Connection object - to which I've already provided host, port, username and password.

Am I doing something wrong? Is there an easier/different way to do this with the new APIs?

Thanks.

Andy Straw University of Rochester

private static HttpClientContext buildHttpContext( Connection labkeyConnection ) throws MalformedURLException {
		URL labkeyBaseUrl = new URL( labkeyConnection.getBaseUrl() );
		HttpHost labkeyHost = new HttpHost( labkeyBaseUrl.getHost(), labkeyBaseUrl.getPort(), labkeyBaseUrl.getProtocol() );
		CredentialsProvider credsProvider = new BasicCredentialsProvider();
		credsProvider.setCredentials(	new AuthScope(labkeyHost),
						new UsernamePasswordCredentials(labkeyConnection.getEmail(), labkeyConnection.getPassword()) );
		AuthCache authCache = new BasicAuthCache();
		authCache.put( labkeyHost, new BasicScheme());
		HttpClientContext httpContext = HttpClientContext.create();
		httpContext.setCredentialsProvider(credsProvider);
		httpContext.setAuthCache(authCache);
		return httpContext;
	}

Andy

I think this is due to a change in the way that HttpClient 4.x deals with "preemptive" authentication, relative to the approach in 3.x. I have an idea of a way to make this easier within the Java client API, but would like to test it with the same URL that you're hitting in this case. From your code, I'm assuming that it's not an "API" URL, which means that it won't challenge the client for Basic Auth credentials, resulting in sending back the login page.

Can you share the controller/action from your URL?

Thanks, Josh

/list/MyContainerPathGoesHere/download.view?entityId=a8cd2f13-a660-1032-96ac-a38b824db812&name=GateTemplate.txt

I have run into another problem with this. The code above works from an external program where I can specify the username and password when I run the app. But it doesn't work when part of a transformation script where I'm authenticating by grabbing the JSESSIONID cookie name and value off the script command line, and calling addCookie() on the Connection. Calling addCookie() works if I'm using the Connection with the Labkey client API (authenticates fine), but does not work with the CloseableHttpClient object I get from that Connection. Just as when using username/password, that Client object does not have any of the authentication info that I gave the Connection, and so I have to (essentially) re-authenticate separately with the Client. So far, I haven't figure out how to do that using a cookie. As I said before: in 14.3, I didn't have to jump through any of these hoops. The executeMethod() method on Connection did all the hard work for me; but that method is no longer in the Connection API as of 15.1.

Thanks.

Andy

Andy

With revision 38038 in the trunk, I made a change that enables this usage pattern:

Connection cn = Connection("http://localhost/labkey", "jeckels@labkey.com", "PASSWORD"); CloseableHttpClient httpClient = cn.ensureAuthenticated(); HttpGet get = new HttpGet(url); CloseableHttpResponse response = httpClient.execute(get); HttpEntity entity = response.getEntity(); String fileContents = EntityUtils.toString(entity);

I think this fits what you've requested, but please let me know.

Thanks, Josh

Thanks, Josh