[ 
https://issues.apache.org/jira/browse/HDFS-16563?focusedWorklogId=763398&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-763398
 ]

ASF GitHub Bot logged work on HDFS-16563:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 28/Apr/22 09:56
            Start Date: 28/Apr/22 09:56
    Worklog Time Spent: 10m 
      Work Description: steveloughran commented on PR #4241:
URL: https://github.com/apache/hadoop/pull/4241#issuecomment-1111997285

   looks like there are some big assumptions about the nested stack trace 
coming back. so please restore that change and see what happens
   
   if the issue is that toString leaks a secret, it should be fixed at that 
level, as it is likely to end up in logs. we don't want any output to expose 
secrets.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 763398)
    Time Spent: 1h  (was: 50m)

> Namenode WebUI prints sensitve information on Token Expiry
> ----------------------------------------------------------
>
>                 Key: HDFS-16563
>                 URL: https://issues.apache.org/jira/browse/HDFS-16563
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Renukaprasad C
>            Assignee: Renukaprasad C
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: image-2022-04-27-23-01-16-033.png, 
> image-2022-04-27-23-28-40-568.png
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Login to Namenode WebUI.
> Wait for token to expire. (Or modify the Token refresh time 
> dfs.namenode.delegation.token.renew/update-interval to lower value)
> Refresh the WebUI after the Token expiry.
> Full token information gets printed in WebUI.
>  
> !image-2022-04-27-23-01-16-033.png!



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

Reply via email to