[ 
https://issues.apache.org/jira/browse/HDDS-13915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18062048#comment-18062048
 ] 

Navin Kumar commented on HDDS-13915:
------------------------------------

Validated this issue the fixed has already done as part of HDDS-14016 
[https://github.com/apache/ozone/blob/9f4fb5e5868a6d90e572bdcbbcc7626c1e1127c9/hado[…]rk/src/main/java/org/apache/hadoop/hdds/server/OzoneAdmins.java|https://github.com/apache/ozone/blob/9f4fb5e5868a6d90e572bdcbbcc7626c1e1127c9/hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/server/OzoneAdmins.java#L156C40-L156C66]
Hence we can close this Jira 

cc:[~Sammi] 

 

> Improve ozone administrator property value tolerance
> ----------------------------------------------------
>
>                 Key: HDDS-13915
>                 URL: https://issues.apache.org/jira/browse/HDDS-13915
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Sammi Chen
>            Assignee: Jitendra Shukla
>            Priority: Major
>         Attachments: image-2025-11-12-13-52-20-881.png
>
>
> Recently, we see follow failure in SCM startup due to there is an extra space 
> used in ozone.administrators configuration
> {code:java}
> Error during updating CA list
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.authorize.AuthorizationException):
>  User scm/[email protected] (auth:KERBEROS) is not authorized 
> for protocol interface
> org.apache.hadoop.hdds.protocol.SCMSecurityProtocol: denied by configured ACL
> {code}
>  !image-2025-11-12-13-52-20-881.png! 
> It's better to make the property value parse more tolerance,  tolerate extra 
> space before and behind each value seperated by ",". 
> This idea applies to all properties, which support to accept a list of 
> values. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to