[SalesForce] Named Credentials in wsdl2apex Class

I have a few questions regarding Named Credentials. I need to perform a SOAP based call out to an external system from Sales Force. I used the wsdl2apex function to generate the class for the call out. When I started integrating this class into my process I got to thinking about securely storing the username and password for the call out, which led me to discover Named Credentials. Question is, can Named Credentials be used in the auto-generated apex class? If so, could you please provide an example?

Thanks in advance

Best Answer

UPDATE for Winter `16 - Simplify Development of Web Service Callouts by Using Named Credentials

Short answer. No, it doesn't appear Named Credentials are supported by Wsdl2Apex.

I created minimal Named Credential for a public webservicex web service that doesn't require authentication (to check if it will work for the endpoint URL).

enter image description here

Then I tried to change the wsdl2Apex generated classes endpoint_x to use it.

wwwWebservicexNet.GlobalWeatherSoap ws = new wwwWebservicexNet.GlobalWeatherSoap();
ws.endpoint_x = 'callout:webservicex';

string weather = ws.GetWeather('Paris / Le Bourget', 'France');
System.debug(weather);

This gives:

System.CalloutException: IO Exception: unknown protocol: callout

In the past I've used protected custom settings within a managed package to store the credentials that are passed to a SOAP web service. As a hierarchy setting I can store Org, Profile, or User level credentials. When deployed as a managed package the credentials can only be accessed by the Apex defined within the package (this includes setting the values as well as retrieval).

Out of interest, I used the FuseIT SFDC Explorer (Disclosure: Made by my current employer) to generate a method from the WSDL that uses HttpRequest and a manual SOAP body rather than WebServiceCallout.invoke.

wwwWebservicexNet.GlobalWeatherSoap ws = new wwwWebservicexNet.GlobalWeatherSoap();
ws.endpoint_x = 'callout:webservicex';
string weather = ws.GetWeather_Http('Paris / Le Bourget', 'France');
System.debug(weather);

Success!

enter image description here

This isn't really Wsdl2Apex anymore as it is using an HttpRequest. It is however calling the SOAP based web service from Salesforce using details stored in a Named Credential.

Related Solutions

[SalesForce] Invalid Session id in Wsdl2Apex

You will need to correctly set the SessionHeader on the instance of CaseCreationUtility.CS_CaseCreationUtility. You don't need to set the session id in the inputHttpHeaders_x map.

E.g.

CaseCreationUtility.CS_CaseCreationUtility stub = new CaseCreationUtility.CS_CaseCreationUtility();
ts.SessionHeader = new CaseCreationUtility.SessionHeader_element();
ts.SessionHeader.sessionId = oauth.access_token;

You may also need to adjust the endpoint URL if it differs from the Org that it was generated from.

// You will need to set the instance (here na5) 
// to match the origin of the sessionId
ts.endpoint_x = 'https://na5.salesforce.com/services/Soap/class/OptionalNamespaceHere/CaseCreationUtility';

The requested oAuth session id should have the full or api scopes to be able to access the web service. The session should be to the same org where the Apex web service is implemented.

If it doesn't work initially with the oAuth derived session, try getting the web session id from the sid cookie or via anonymous Apex with UserInfo.getSessionId().

[SalesForce] Using Named Credentials to get Salesforce sessionId

You can do this, but you'll need to do a bit more work to use it.

First, Create a connected app with oAuth, select refresh_token (at a min) for the oAuth scope
Second, Create an auth provider of the salesforce type. Give it the oauth consumer key and consumer secret that you got when you created the connected app.
Finally, create a Named Credential using oauth, and your auth provider. When you save the named credential, it will prompt you to log in to a SF org.

Once you've logged in there, the refresh token is saved and used by the named credential. From there, you can make callouts to access data. Note whatever user you login as there is the user your api calls will run as.

Best Answer

Related Solutions

[SalesForce] Invalid Session id in Wsdl2Apex

[SalesForce] Using Named Credentials to get Salesforce sessionId

Related Topic