[
https://issues.apache.org/jira/browse/HDDS-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724494#comment-16724494
]
Ajay Kumar commented on HDDS-929:
---------------------------------
[~xyao] Even if we need this validation it should be done by done at key pair
generation time. In our case it will be some implementation of
CertificateClient.
> Remove ozone.max.key.len property
> ----------------------------------
>
> Key: HDDS-929
> URL: https://issues.apache.org/jira/browse/HDDS-929
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Ajay Kumar
> Assignee: Ajay Kumar
> Priority: Major
> Attachments: HDDS-929-HDDS-4.00.patch
>
>
> Generation of secret key in OzoneSecretManager is different from hadoop
> SecretManager. Since key-pair generation is not the responsibility of
> {{OzoneSecretManager}}/{{OzoneSecretKey}} we don't need maxKeyLen related
> checks inside them. Jira proposes to remove ozone.max.key.len.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
