Hello @dgudkov,
The idea is to streamline the process for the client, not having them download additional software/authentication processes. How would the user pass the Salesforce connector to us from his own desktop version, if we have the connectors in our EasyMorph Server? Would they have to connect to EasyMorph Server from desktop?
The authentication process (not only for Salesforce, but any web location connector with OAuth2 authentication) that I was thinking of could go like this:
-
Internally, first we configure the details of the connector (OAuth2 Client, Secret, Callback URL (would be a specific URL in EM Server where the server is listening), scopes, etc.)
-
Once that is done, we create an EasyMorph Project for OAuth2 authentication (1 per client per connector). This EasyMorph project gets launched through an API call (by the client) and consists of the following:
- A) Once the task is triggered, an email action sends the client the link to do the OAuth2 authentication. (In the background, EasyMorph Server is listening for when the user enters their login details and gives permission to EasyMorph).
- B) The user clicks on the link, logs into Salesforce, and gives permission to EasyMorph. EasyMorph Server is listening in a certain callback URL for the code, and once that is done the connector is authenticated.
- C) If in the future the client loses authentication, they have to repeat the same process - launch the task externally, receive an email, login/give permission and then the connector is authenticated again.
In my opinion, having a process like this where EM Server acts as a bridge for streamlining the authentication, makes it easier both for the client and us.
I feel it has certain relation to what @RJO mentions in his post “Big feature request on all cloud connectors”, regarding having an action inside a project to authenticate. In this case, it would be used in EasyMorph Server to authenticate a Web Location connector with OAuth2 authentication.
What do you think?
Thanks!
Roberto