You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@sentry.apache.org by "Dapeng Sun (JIRA)" <ji...@apache.org> on 2014/12/23 03:12:13 UTC

[jira] [Updated] (SENTRY-595) [UnitTest] In Kerberos mode, client should run under clientSubject

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

Dapeng Sun updated SENTRY-595:
------------------------------
    Summary: [UnitTest] In Kerberos mode, client should run under clientSubject  (was: [UnitTest]In Kerberos mode, client should run under clientSubject)

> [UnitTest] In Kerberos mode, client should run under clientSubject
> ------------------------------------------------------------------
>
>                 Key: SENTRY-595
>                 URL: https://issues.apache.org/jira/browse/SENTRY-595
>             Project: Sentry
>          Issue Type: Bug
>            Reporter: Dapeng Sun
>            Assignee: Dapeng Sun
>         Attachments: SENTRY-595.001.patch
>
>
> Working with [~colinma] on SENTRY-296, we found client will throw a Kerberos exception when do some operations like renew {{client}} in Kerberos related UnitTests. The root cause is in some test {{client}} didn't run under {{clientSubject}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)