1

Generally, we use username-password based authentication mechanism if we want external application to consume our Salesforce SOAP webservice. And for calling SF REST webservice we need to create connected app so that we get the client id and secret key for authenticating with Salesforce.

But can we do the other way round, meaning, just wondering, Is it possible for the external systems to call Salesforce SOAP webservice using Connected app (client id and secret key) for authentication?

Or is it like we can't use Connected app in case of SOAP based webservices?

Improve this question

1 Answer 1

Reset to default
0

As long as you use the OAuth flow (via Connected App), you can use the Access Token you received with any API (as long as you have the correct scope). It's as a simple as using the Access Token in the sessionId SessionHeader property.

Improve this answer
3
  • Okay, so which means In case of SOAP webservice as well, I can use Client ID and secret key (received in Connected app) for authentication and the access token that I will receive , I can copy it in session Id tag? Is that correct? Is yes, then what could be the difference between session Id and access token even though they both can authenticate?
    – sfdc07
    Commented Dec 9, 2021 at 9:56
  • @sfdc07 AT can be limited by "scope" of the Connected App, and the manner of acquisition are different (OAuth flow versus SOAP login call). Technical differences aside, AT and SID serve the same purpose; to allow access to Salesforce resources. However, AT is called AT because that term comes from the OAuth specification, while SID comes from the normal nomenclature used by many SOAP-based logins.
    – sfdcfox ♦
    Commented Dec 9, 2021 at 12:43
  • Perfect, that make sense. Thank you!
    – sfdc07
    Commented Dec 9, 2021 at 12:58

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .