Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-5881 Change S3G to OM RPC framework to keep persistent connection across multiple users
  3. HDDS-5883

Authenticate with OM as S3G (Client side)

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.3.0
    • None

    Description

      S3G now has kerberos identity added as part of fixes for reading encrypted buckets. 

      S3G will no longer proxy the S3 API users' credentials but will authenticate itself for secure Hadoop RPC communication.

      Thus, as far as Hadoop RPC is concerned it will validate S3G as a secure entity talking with OM.

      Attachments

        Issue Links

          causes

          Task - A task that needs to be done. HDDS-6325 Fix interface ClientProtocol methods typo setThreadLocalS3Auth and clearThreadLocalS3Auth

          • Major - Major loss of function.
          • Resolved
          is cloned by

          Sub-task - The sub-task of the issue HDDS-5884 OM Validate S3 Auth for write requests

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link GitHub Pull Request #2775

          Activity

            People

              ritesh Ritesh Shukla
              ritesh Ritesh Shukla
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: