[
https://issues.apache.org/jira/browse/HDDS-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789283#comment-17789283
]
István Fajth commented on HDDS-9442:
------------------------------------
Actually I realized, it is not HDDS-8879 which was initially fixed the issue by
accident.
The issue is fixed since HDDS-7339, as in that commit, we started to store a
reference for the scm security client, and during initialization, when the
update of the CA list was running, the client was created with the correct
login context.
HDDS-8879 later reworked the code and pulled the scm secuirty client creation
to the OzoneManager class.
> Token verification from OMs at DT renew happens in the wrong login context.
> ---------------------------------------------------------------------------
>
> Key: HDDS-9442
> URL: https://issues.apache.org/jira/browse/HDDS-9442
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Manager, Security
> Reporter: István Fajth
> Assignee: István Fajth
> Priority: Critical
> Fix For: 1.4.0
>
>
> In case an OM Leader change happens, none of the longer running jobs that are
> using Delegation Tokens can use the cluster anymore and fail. (reported by
> [~pifta]
> More details to be filled in later.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
