Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-19166

Add @Secret annotation to the configuration framework

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Critical
    • Resolution: Done
    • None
    • 3.0
    • rest

    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

      Attachments

        Issue Links

          blocks

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-19167 Support @Secret annotation on the configuration storage layer

          • Critical - Crashes, loss of data, severe memory leak.
          • Open
          is blocked by

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-19165 ConfigurationVisitor should know about annotations of configuration fields

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-18950 REST should mask sensitive information

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          links to

          Web Link GitHub Pull Request #2073

          Activity

            People

              ivan.gagarkin Ivan Gagarkin
              ivan.gagarkin Ivan Gagarkin
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: