zhiliang-wu opened a new pull request, #13300:
URL: https://github.com/apache/seatunnel/pull/13300
<!--
Thank you for contributing to SeaTunnel! Please make sure that your code
changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.
Feel free to ping committers for the review!
## Contribution Checklist
- Make sure that the pull request corresponds to a [GITHUB
issue](https://github.com/apache/seatunnel/issues).
- Name the pull request in the form "[Feature] [component] Title of the
pull request", where *Feature* can be replaced by `Hotfix`, `Bug`, etc.
- Minor fixes should be named following this pattern: `[hotfix] [docs] Fix
typo in README.md doc`.
-->
### Purpose of this pull request
Currently, `connector-maxcompute` transitively inherits
`com.aliyun:credentials-java:0.3.12` from `odps-sdk-core:0.51.2-public`.
This PR explicitly upgrades `com.aliyun:credentials-java` to version `1.0.8`
in `connector-maxcompute/pom.xml`.
#### Strictly Limited Scope & Impact:
* Confined strictly to AklessAccount auth: In the entire
connector-maxcompute module, credentials-java is referenced in only a single
line in MaxcomputeUtil.getAccount():
`return new AklessAccount(new DefaultCredentialsProvider());`
* No impact on static credentials: All jobs configured with static
credentials (access_id / access_key via AliyunAccount or sts_token via
StsAccount) are 100% unaffected because they rely solely on internal ODPS SDK
classes without invoking credentials-java.
* Zero change to runtime data plane: Data reading, writing, table tunnel,
split assignment, type conversion, and catalog operations remain completely
untouched.
#### Key Advantages of this Upgrade:
1. Private VPC STS Endpoint Routing (OIDC / RRSA):
- In private Kubernetes/ACK clusters without public internet egress, pods
exchange OIDC tokens for STS tokens via internal VPC endpoints.
- credentials-java:1.0.8 introduces dynamic VPC endpoint computation via
ALIBABA_CLOUD_VPC_ENDPOINT_ENABLED=true and ALIBABA_CLOUD_STS_REGION,
automatically resolving the STS endpoint to sts-vpc.<region>.aliyuncs.com
instead of hardcoding to public sts.aliyuncs.com.
2. Resilient Token Rotation & Asynchronous Refresh:
- Modernized credential lifecycle with proactive, non-blocking
asynchronous token refresh before expiry.
- Robust error handling and graceful fallbacks when OIDC service account
projected volume tokens are rotated on disk by Kubernetes.
3. Enhanced Diagnostics & Debuggability:
- Preserves full transport error details during credential refresh
failures, preventing root network/authentication exceptions from being obscured.
4. Security Enhancements:
- Implements sensitive token and credential value redaction across models
and logs.
5. Ecosystem & SDK V2.0 Interoperability:
- Implements com.aliyun.credentials.api.ICredentialsProvider
(credentials-api:1.0.0), aligning with modern Alibaba Cloud SDK V2.0 standards.
### Does this PR introduce _any_ user-facing change?
<!--
Note that it means *any* user-facing change including all aspects such as
the documentation fix.
If yes, please clarify the previous behavior and the change this PR proposes
- provide the console output, description and/or an example to show the
behavior difference if possible.
If possible, please also clarify if this is a user-facing change compared to
the released SeaTunnel versions or within the unreleased branches such as dev.
If no, write 'No'.
If you are adding/modifying connector documents, please follow our new
specifications: https://github.com/apache/seatunnel/issues/4544.
-->
No backward compatibility breaks. Users running passwordless authentication
via OIDC in private VPC environments can now set
ALIBABA_CLOUD_VPC_ENDPOINT_ENABLED=true to route STS token requests through the
VPC endpoint.
### How was this patch tested?
<!--
If tests were added, say they were added here. Please make sure to add some
test cases that check the changes thoroughly including negative and positive
cases if possible.
If it was tested in a way different from regular unit tests, please clarify
how you tested step by step, ideally copy and paste-able, so that other
reviewers can test and check, and descendants can verify in the future.
If tests were not added, please describe why they were not added and/or why
it was difficult to add.
If you are adding E2E test cases, maybe refer to
https://github.com/apache/seatunnel/blob/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/connector-cdc-mysql-e2e/src/test/resources/mysqlcdc_to_mysql.conf,
here is a good example.
-->
Tested unit test suite in connector-maxcompute (all 90 tests pass).
Added unit test testOIDCRoleArnCredentialProviderVpcEndpointResolution in
MaxcomputeUtilTest to verify VPC STS endpoint resolution.
Code formatted with ./mvnw spotless:apply.
### Check list
* [ ] If any new Jar binary package adding in your PR, please add License
Notice according
[New License
Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/developer/new-license.md)
* [ ] If necessary, please update the documentation to describe the new
feature. https://github.com/apache/seatunnel/tree/dev/docs
* [ ] If necessary, please update `incompatible-changes.md` to describe the
incompatibility caused by this PR.
* [ ] If you are contributing the connector code, please check that the
following files are updated:
1. Update
[plugin-mapping.properties](https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties)
and add new connector information in it
2. Update the pom file of
[seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml)
3. Add ci label in
[label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml)
4. Add e2e testcase in
[seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/)
5. Update connector
[plugin_config](https://github.com/apache/seatunnel/blob/dev/config/plugin_config)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]