[ 
https://issues.apache.org/jira/browse/HBASE-16231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack updated HBASE-16231:
--------------------------
    Release Note: Prior to this change, the integration test clients 
(IntegrationTest*) relied on the Kerberos credential cache for authentication 
against secured clusters.  This could lead to the tests failing due to 
authentication failures when the tickets in the credential cache expired.  With 
this change, the integration test clients will make use of the configuration 
properties for "hbase.client.keytab.file" and "hbase.client.kerberos.principal" 
(They are required).  This will perform a login from the configured keytab file 
and automatically refresh the credentials in the background for the process 
lifetime.  (was: Prior to this change, the integration test clients 
(IntegrationTest*) relied on the Kerberos credential cache for authentication 
against secured clusters.  This could lead to the tests failing due to 
authentication failures when the tickets in the credential cache expired.  With 
this change, the integration test clients will make use of the configuration 
properties for "hbase.client.keytab.file" and 
"hbase.client.kerberos.principal", when available.  This will perform a login 
from the configured keytab file and automatically refresh the credentials in 
the background for the process lifetime.)

> Integration tests should support client keytab login for secure clusters
> ------------------------------------------------------------------------
>
>                 Key: HBASE-16231
>                 URL: https://issues.apache.org/jira/browse/HBASE-16231
>             Project: HBase
>          Issue Type: Improvement
>          Components: integration tests
>            Reporter: Gary Helmling
>            Assignee: Gary Helmling
>            Priority: Major
>             Fix For: 1.3.0, 2.0.0
>
>         Attachments: HBASE-16231.001.patch
>
>
> Integration tests currently rely on an external kerberos login for secure 
> clusters.  Elsewhere we use AuthUtil to login and refresh the credentials in 
> a background thread.  We should do the same here.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to