You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by "Alberne (via GitHub)" <gi...@apache.org> on 2025/06/25 03:39:12 UTC

[I] [Improve][Connector-V2][Http] Http source supports user-defined custom signature algorithms for authentication [seatunnel]

Alberne opened a new issue, #9500:
URL: https://github.com/apache/seatunnel/issues/9500

   ### Search before asking
   
   - [x] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement.
   
   
   ### Description
   
    Http source supports user-defined custom signature algorithms for authentication
   
   ### Usage Scenario
   
   In our scenario, we obtain data from multiple third-party OpenAPIs. Each of these OpenAPIs requires validation of HTTP requests using their own HTTP signature algorithms. Therefore, it is necessary for the HTTP source to support user-defined signature algorithms.
   
   for some example: 
   1. huawei  :https://support.huaweicloud.com/devg-apisign/api-sign-algorithm-001.html
   2. UC: https://docs.ucloud.cn/api/summary/signature
   
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: commits-unsubscribe@seatunnel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Improve][Connector-V2][Http] Http source supports user-defined custom signature algorithms for authentication [seatunnel]

Posted by "Hisoka-X (via GitHub)" <gi...@apache.org>.
Hisoka-X commented on issue #9500:
URL: https://github.com/apache/seatunnel/issues/9500#issuecomment-3190505948

   Why not use SPI? The algorithm logic will not change much, so there is no need to rewrite it in every config file. Using SPI to load custom algorithms may be more universal.


-- 
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: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Improve][Connector-V2][Http] Http source supports user-defined custom signature algorithms for authentication [seatunnel]

Posted by "Hisoka-X (via GitHub)" <gi...@apache.org>.
Hisoka-X commented on issue #9500:
URL: https://github.com/apache/seatunnel/issues/9500#issuecomment-3200743601

   > * **​​Practical Scenario​​**: We integrate with over a dozen third-party OpenAPIs, ​​**80%** of which require distinct signature algorithms​​. The **dynamicCompile** solution enables ​​"code-as-configuration"​​, allowing users to implement custom signatures ​​without modifying the Seatunnel project code​​. This eliminates the need to download the project, build JARs, or redeploy.
   > *
   
   Make sense to me. Thanks @Alberne for explain. Please go head to push this issue.


-- 
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: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Improve][Connector-V2][Http] Http source supports user-defined custom signature algorithms for authentication [seatunnel]

Posted by "Alberne (via GitHub)" <gi...@apache.org>.
Alberne commented on issue #9500:
URL: https://github.com/apache/seatunnel/issues/9500#issuecomment-3002862588

   @Hisoka-X  please assign to me. 
   our branch code has already implemented this feature. Later, I will explain my implementation approach and discuss it with you.


-- 
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: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Improve][Connector-V2][Http] Http source supports user-defined custom signature algorithms for authentication [seatunnel]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #9500:
URL: https://github.com/apache/seatunnel/issues/9500#issuecomment-3120809276

   This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.


-- 
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: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Improve][Connector-V2][Http] Http source supports user-defined custom signature algorithms for authentication [seatunnel]

Posted by "Alberne (via GitHub)" <gi...@apache.org>.
Alberne commented on issue #9500:
URL: https://github.com/apache/seatunnel/issues/9500#issuecomment-3200580544

   > Why not use SPI? The algorithm logic will not change much, so there is no need to rewrite it in every config file. Using SPI to load custom algorithms may be more universal.
   
   hi @Hisoka-X Thank you for your suggestions. I chose the **​​dynamicCompileCode**​​ approach primarily based on two key considerations:
   
   1. **​​Practical Scenario​​**: We integrate with over a dozen third-party OpenAPIs, ​​80% of which require distinct signature algorithms​​. The **dynamicCompile** solution enables ​​"code-as-configuration"​​, allowing users to implement custom signatures ​​without modifying the Seatunnel project code​​. This eliminates the need to download the project, build JARs, or redeploy.
   
   2. ​​**User Experience**​​: For other Seatunnel users, the ​​"code-as-configuration"​​ approach is far more user-friendly, as it simplifies customization while maintaining flexibility.


-- 
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: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Improve][Connector-V2][Http] Http source supports user-defined custom signature algorithms for authentication [seatunnel]

Posted by "Hisoka-X (via GitHub)" <gi...@apache.org>.
Hisoka-X commented on issue #9500:
URL: https://github.com/apache/seatunnel/issues/9500#issuecomment-3200728265

   cc @corgy-w as well.


-- 
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: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Improve][Connector-V2][Http] Http source supports user-defined custom signature algorithms for authentication [seatunnel]

Posted by "Alberne (via GitHub)" <gi...@apache.org>.
Alberne commented on issue #9500:
URL: https://github.com/apache/seatunnel/issues/9500#issuecomment-3190470036

   hi @Hisoka-X The design approach is as follows:
   
   in our private branch, the HTTP source uses hard-coded custom classes to implement HTTP signatures. This implementation method, which intrudes into the project code, is not user-friendly. Therefore, I referenced the DynamicCompile approach of the `transform component` to enable customers to customize their signature algorithms.
   
   - in our private branch:
   
   <img width="501" height="651" alt="Image" src="https://github.com/user-attachments/assets/1a837974-f6f2-4954-b798-e800f2271fa6" />
   
   
   -  contributed to the community branch:
   
   <img width="384" height="562" alt="Image" src="https://github.com/user-attachments/assets/665567bd-d4b5-4692-b1d6-c711b380d1ed" />
   


-- 
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: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Improve][Connector-V2][Http] Http source supports user-defined custom signature algorithms for authentication [seatunnel]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #9500: [Improve][Connector-V2][Http] Http source supports user-defined custom signature algorithms for authentication
URL: https://github.com/apache/seatunnel/issues/9500


-- 
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: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Improve][Connector-V2][Http] Http source supports user-defined custom signature algorithms for authentication [seatunnel]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #9500:
URL: https://github.com/apache/seatunnel/issues/9500#issuecomment-3146060443

   This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.


-- 
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: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org