[
https://issues.apache.org/jira/browse/HADOOP-11837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498406#comment-14498406
]
Haohui Mai commented on HADOOP-11837:
-------------------------------------
There are two use cases here:
* HttpServer2 creates and owns the SignerSecretProvider, meaning that the
SignerSecretProvider will be destroyed by the HttpServer2.
{{AuthenticationFilter}} should not call {{destroy()}}.
* The Tomcat server initializes {{AuthenticationFilter}} through
{{AuthenticationFilterInitializer}}. This is the use case of Oozie. In this
case the AuthenticationFilter should call the {{destroy()}} method of the
{{SignerSecretProvider}} when its life cycle ends.
> After HADOOP-11754, oozie fails to stop cleanly
> -----------------------------------------------
>
> Key: HADOOP-11837
> URL: https://issues.apache.org/jira/browse/HADOOP-11837
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 2.7.0
> Reporter: Venkat Ranganathan
> Assignee: Venkat Ranganathan
> Priority: Blocker
> Fix For: 2.7.0
>
> Attachments: HADOOP-11837.patch
>
>
> After HADOOP-11754, AuthenticationFilter has to be enhanced to destroy to
> secret provider. Else, products like Oozie which extend the
> AuthenticationFilter fail to stop
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
