[Bug][S3] Unable to access S3 using role and webIdentityTokenFile in WebIdentityTokenFileCredentialsProvider

Description

env {
  parallelism = 1
  job.mode = "STREAMING"
  checkpoint.interval = 10000
}

source {
  MySQL-CDC {
    plugin_output = "fake"
    base-url = "jdbc:mysql://test:3306/test"
    username = "***"
    password = "****"
    
    table-names = ["test.user"]
    table-names-config = [
      {
        table = "test.user"
        primaryKeys = ["id"]
      }
    ]
  }
}

transform {
  Sql {
    plugin_input = "fake"
    plugin_output = "fake1"
    query = "select id, open_id from user"
  }
}

sink {
  Hive {
    plugin_input = "fake1"
    table_name = "tmp.test_hive_sink_on_s3"
    metastore_uri = "thrift://ip-xxx-xx-1-142.cn-north-1.compute.internal:9083"
    hive.hadoop.conf = {
        bucket="s3a://xxxxxxx"
        fs.s3a.endpoint="s3.cn-north-1.amazonaws.com.cn"
        fs.s3a.aws.credentials.provider="org.apache.hadoop.fs.s3a.WebIdentityTokenFileCredentialsProvider" //期望
    }
  }
}

Contributor guide

Tech stack

javaaws

Domain

databackend

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

mostly clear

Prerequisites

JavaAWS S3 basicsSeaTunnel plugin structureHadoop configuration

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

35

Research direction

Investigate the current S3 sink implementation in SeaTunnel, specifically the Hive sink that uses Hadoop S3A filesystem. Look for how credentials are configured via `fs.s3a.aws.credentials.provider` in the configuration. The goal is to add support for `WebIdentityTokenFileCredentialsProvider` from the AWS SDK. Relevant files are likely in `seatunnel connector flink` or `seatunnel connector spark` under `hive` or `s3` packages. Check existing credential providers and extend the configuration parsing to accept the new provider class name and any required parameters (like role ARN and web identity token file path). The issue refers to Apache Hadoop's S3A connector and AWS SDK's `software.amazon.awssdk.auth.credentials.WebIdentityTokenFileCredentialsProvider`.