Salesforce.com Integration with Service-Now

[#1]

We have the implemented the salesforce,com integration, but cannot get the webservice SFDC_Case to work properly. Outbound messages from SFDC are not being delivered ("unauthorized").

SFDC are telling us that
"Service-Now would need to make a branch of the server publicly addressable, and then place the Webservice in this branch (this would also require that our outbound message be modified to reflect against the new endpoint"

Does this sound familiar to anyone who has integrated the two applications?
Any suggestions most welcome

john naughton

[DavidLoo]

John, the SFDC outbound message needs to post to Service-now using a basic authentication header of a username password that exists in Service-now. In the event that it is unable to post using basic auth, in your instance's System Properties -> Web Services, you will have to disable basic authorization for incoming SOAP requests, for un-authenticated services to come in.

[monkalope]

David: Does that leave things open for malicious or potential threats? We have the same issue happening on our Outbound messages.
Monkalope

[Valor1]

I just did a SFDC integration, and AFAIK, they do not support basic auth in web services.

The auth from Service-Now to SFDC does work fine. You have to generate an application key, and append it to the beginning of the account password you've set in the SFDC properties.

[Valor1]

It's been a while, but to clarify, I believe the "application key" is the same as the "security token" spoken of here: https://login.salesforce.com/help/doc/en/user_security_token.htm