Attach filesAttach ScreenshotVotersStop watchingWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • None
    • None
    • HDDS BadLands

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            ajayydv Ajay Kumar
            ajayydv Ajay Kumar
            Votes:
            0 Vote for this issue
            Watchers:
            4 Stop watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Agile

                Completed Sprint:
                HDDS BadLands ended 05/Aug/19
                View on Board

                Slack

                  Issue deployment