Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6DC29D286 for ; Tue, 24 Jul 2012 01:41:36 +0000 (UTC) Received: (qmail 72624 invoked by uid 500); 24 Jul 2012 01:41:36 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 72488 invoked by uid 500); 24 Jul 2012 01:41:35 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 72339 invoked by uid 99); 24 Jul 2012 01:41:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jul 2012 01:41:35 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id C1412142823 for ; Tue, 24 Jul 2012 01:41:35 +0000 (UTC) Date: Tue, 24 Jul 2012 01:41:35 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: issues@hbase.apache.org Message-ID: <1905929512.93887.1343094095793.JavaMail.jiratomcat@issues-vm> In-Reply-To: <777736690.93535.1343088274922.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HBASE-6444) Expose the ability to set custom HTTP Request Headers for the REST client used by RemoteHTable MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421090#comment-13421090 ] Andrew Purtell commented on HBASE-6444: --------------------------------------- Right, pardon the dumb question. What I meant was use the HttpClient directly but if there's still some convenience afforded by the REST client classes we can add request configuration callbacks, no problem. > Expose the ability to set custom HTTP Request Headers for the REST client used by RemoteHTable > ---------------------------------------------------------------------------------------------- > > Key: HBASE-6444 > URL: https://issues.apache.org/jira/browse/HBASE-6444 > Project: HBase > Issue Type: Improvement > Components: rest > Reporter: Erich Hochmuth > Attachments: HBASE-6444-0.94.patch, HBASE-6444.patch > > Original Estimate: 48h > Remaining Estimate: 48h > > My corporate security office (ISO) requires that all http traffic get routed through a Web Access Management layer (http://en.wikipedia.org/wiki/Web_access_management) > Our Hadoop cluster has been segmented by a virtual network with all access to HBase from outside clients being managed through HBase Stargate rest server. > The corporate WAM system requires that all http clients authenticate with it first before making any http request to any http service in the corporate network. After the http client authenticates with the WAM system the WAM system returns the client a set of values that must be inserted into a http cookie and request header of all future http requests to other http clients. > This would mean that all requests through the RemoteHTable interface would require that this cookie and request header be set as part of the http request. org.apache.hadoop.hbase.rest.client.Client looks like the appropriate place that this functionality would need to be plugged into. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira