zoomingrocket opened a new issue, #4657:
URL: https://github.com/apache/hop/issues/4657
### What would you like to happen?
### Feature Request: OAuth Authentication Support for Salesforce Integration
**Summary:**
To enhance security and comply with evolving Salesforce policies, we propose
adding OAuth authentication support for Salesforce Input/Output operations in
our product.
**Background:**
Many companies are adopting stricter security measures for their Salesforce
Organizations, requiring all API access to be conducted via a Connected App
using OAuth. This policy renders the standard SOAP API login() call with
username, password, and security token ineffective. Instead, an OAuth handshake
must be performed to generate a bearer token, which is then used in the SOAP
"sessionID" header for all Salesforce SOAP calls.
**Proposed Solution:**
1. **OAuth Authentication Mechanism:**
- Implement OAuth as an authentication option within Salesforce
Input/Output operations.
- Allow users to perform the OAuth handshake and generate a bearer token.
2. **REST Client Integration:**
- Enable the REST Client to generate an OAuth bearer token.
- Allow the insertion of the "sessionID" SOAP header parameter for
Salesforce Input/Output operations without requiring additional
username/password setup.
**References:**
- Salesforce OAuth and SOAP API:
https://developer.salesforce.com/blogs/developer-relations/2011/03/oauth-and-the-soap-api
- Other ETL Vendors Reference:
https://knowledge.informatica.com/s/article/515185?language=en_US
This feature will align our product with current security practices and
ensure seamless integration with Salesforce for our users.
### Issue Priority
Priority: 2
### Issue Component
Component: Hop Gui
--
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]
