Marketo Salesforce Sync ( Connected App )

[Dhanush_Ganesh]

Hello there,

I have a question regarding the Marketo Salesforce Sync. Quick backgroundd : The Current team did not set up the Integration.

Recently our Salesforce team did a Salesforce Sandbox refresh and we re-synced MKTO and Salesforce using OAuth login ( using Connected App ). The SF team re-created the Connected App and used Consumer Key and  secret to re-establish the connection. However when our SF team checked for the Connected App in Production environment, it was not available but the two systems are connected and running perfectly.

Our concern here is there is no Connected App in Salesforce Production and SF team raised a support request with SF and they got this below feedback

"Please note, If a connected app is part of managed package and if we want to see it in the org then we should install that app.
Also, if the connected app is part of a managed package then we can not access the consumer key and secret of that app. It is working as designed."

The SF team is unsure how MKTO and SF got connected initially. The real question is – should we be concerned?  Will our integration break without this?

Thanks!

[Darshil_Shah1]

Could there be an issue at Salesforce's end where-in the connected app even though got synced over, but for some reason isn't visible? The connected app for the Marketo sync needs to be created as a custom-connected app, i.e., it isn't a part of any package. If the OAuth sync was set up initially, then I don't think it would have been possible w/o creating a connected app in SFDC. Do you see any sync failures for new/existing records as of now?

For some background, Marketo recommends reaching out to support if users are doing a total sandbox refresh activity as that changes the org id of SFDC which requires intervention from the Marketo support team for updating the org id in the backend. Without updating the org-id post total sandbox refresh activity, Marketo and SFDC may seem connected but it's likely that many things will no longer get synced correctly.

However, in the case of just the sandbox data refresh activity, the org id doesn't get changed; hence, users don't need to reach out to support for updating the SFDC org id for their Marketo sync in the backend.

[Dhanush_Ganesh]

Hi @Darshil_Shah1 thanks for the response.

On the total sandbox refresh, we reached out to the support and all is well with Sandbox as we connected it by again creating the Connected App in Salesforce and used the Consumer Key and Secret to update the same in MKTO and re-establish the sync.

However, our Salesforce Admin couldn't find the Connected App that's created in Production instance. All being said, the connection is seamless with the Production instances. The only concern for SF team is they couldn't find the Connected App and they raised the support request with SF and they came back with this answer ""Please note, If a connected app is part of managed package and if we want to see it in the org then we should install that app.
Also, if the connected app is part of a managed package then we can not access the consumer key and secret of that app. It is working as designed."

Wondering if there is another way that our SF team would have connected MKTO other than OAuth. ( Even though our instance show 'Edit OAuth settings" in Admin>Salesforce.

I will ask to check our SF team again with their support

[Darshil_Shah1]

For the newer subscription, customers have the option of syncing with SFDC using OAuth sync, for the rest, OAuth sync needs to be enabled by Marketo. Assuming that the SFDC team has sufficient rights to see the connected app, not being able to see the connected app doesn't make the sense as you mention that sync is working as expected. Addressing the response from the SFDC support team, the connected app that is created in SFDC is a custom one and isn't included/part of any SFDC package, so ideally you should be able to see it in the org.

Another way of integrating SFDC with Marketo is by using basic authentication, wherein the integration is done by entering the security token along with the sync user's id and password. Unlike OAuth-based integration, the basic auth doesn't need to create a connected app in SFDC for syncing.

Since you specifically mentioned that you've re-established the SFDC and Marketo using the connected app's id and secret creds, it is evident that you've OAuth provisioned in your instance for the sync. Just to double-check, I'd recommend verifying that the SFDC team has sufficient rights to access the connected app in the org.