You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ivan Gagarkin (Jira)" <ji...@apache.org> on 2023/03/30 08:51:00 UTC

[jira] [Updated] (IGNITE-19166) Add @Secret annotation to the configuration framework

     [ https://issues.apache.org/jira/browse/IGNITE-19166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Gagarkin updated IGNITE-19166:
-----------------------------------
    Description: 
We should mask sensitive information on the configuration level via org.apache.ignite.internal.configuration.tree.ConfigurationVisitor

 
 * Create MaskConfigurationVisitor, which checks @Secret annotation and returns a masked value, if the annotation is present.
 * Use the visitor in the REST.
 * Remove JsonMasker

  was:
We should mask sensitive information on the configuration level via org.apache.ignite.internal.configuration.tree.ConfigurationVisitor

 

Create MaskConfigurationVisitor, which checks @Secret annotation and returns a masked value, if the annotation is present. 


> Add @Secret annotation to the configuration framework
> -----------------------------------------------------
>
>                 Key: IGNITE-19166
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19166
>             Project: Ignite
>          Issue Type: Improvement
>          Components: rest
>            Reporter: Ivan Gagarkin
>            Priority: Critical
>              Labels: ignite-3
>
> We should mask sensitive information on the configuration level via org.apache.ignite.internal.configuration.tree.ConfigurationVisitor
>  
>  * Create MaskConfigurationVisitor, which checks @Secret annotation and returns a masked value, if the annotation is present.
>  * Use the visitor in the REST.
>  * Remove JsonMasker



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