Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Multiple API calls for SOAP connector

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on May 8 2020 at 20:35 UTC

Hi,


We want to implement multiple API calls for the SOAP connector. Individual calls are working fine, but when I try to chain them together in the createaccountjson, it does not work. Any help would be appreciated. Thank you!

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.
4 REPLIES 4

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on May 15 2020 at 02:40 UTC

Hi Manisha,


Please refer below document.

https://saviynt.freshdesk.com/support/solutions/articles/43000505309-soap-connector-guide


Thanks

Ajay

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on May 26 2020 at 15:50 UTC

Manisha,


I am not even able to get my single API call Connector working. The Saviynt documentation on the SOAP Connector is pathetic. The examples JSONs given in the document even failed the JSONLint validator. Probably never tested.


Can you give me working examples of the following?

  • CONNECTIONJSON
  • SOAP_ENDPOINT
  • HR_IMPORT_JSON


Please use Dummy data for credentials, URL etc. All I need is the format so I can configure mine.


Anand

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on May 27 2020 at 03:27 UTC

Hi Anand,


PFA Samples


Connection JSON


{

"authentications": {

"login": {

"properties": {

"SOAP_ENDPOINT": "https://login.ss.com",

"USERNAME": "a@st.com",

"PASSWORD": "Saviyntsf1o0XuHjxaIFrZIoMFKfNOtnSC",

"REQUESTPARAMS" : {

"Content-Type" : "text/xml",

"SOAPAction" : ""

}

}

}

}

}


HR_Import_JSON:


{

"REQUESTXML1": "<Envelope xmlns=\"http://schemas.xmlsoap.org/soap/envelope/\"><Body><login xmlns=\"urn:enterprise.soap.com\"><username>nu@s.com</username><password>SSC</password></login></Body></Envelope>",

"REQUESTPARAMS1" : {

"Content-Type" : "text/xml",

"SOAPAction" : ""

},

"RESPONSEDATAPATH1" : "Body.loginResponse.result",

"RESPONSEMAPPING1" : {

"TOKEN" : "sessionId"

},

"REQUESTXML2": "<Envelope xmlns=\"http://schemas.xmlsoap.org/soap/envelope/\"><Header><SessionHeader xmlns=\"urn:enterprise.soap.com\"><sessionId>${TOKEN}</sessionId></SessionHeader><QueryOptions xmlns=\"urn:enterprise.soap.com\"><batchSize>1000</batchSize></QueryOptions></Header><Body><queryAll xmlns=\"urn:enterprise.soap.com\"><queryString>SELECT FirstName, LastName, ID, Name, Profile.Name, profileId, userType, email, userName, AccountId, Alias, IsActive, Phone, PortalRole, Title, UserRoleId FROM User</queryString></queryAll></Body></Envelope>",

"REQUESTPARAMS2" : {

"Content-Type" : "text/xml",

"SOAPAction" : ""

},

"RESPONSEDATAPATH2": "Body.queryAllResponse.result.records",

"USERMAPPING2": "USERNAME:Email,CUSTOMPROPERTY6:Id,FIRSTNAME:Name,CUSTOMPROPERTY1:Username,CUSTOMPROPERTY2:ProfileId,CUSTOMPROPERTY3:FirstName,CUSTOMPROPERTY4:LastName,CUSTOMPROPERTY5:IsActive"

}


Thanks

Ajay

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on June 3 2020 at 21:59 UTC

Ajay,

I am trying to configure this SOAp Connection and getting a 500 Server Error.

This connection is working perfectly in SOAPUI as well as Postman.

Can you tell me what cound be wrong?


CONNECTIONJSON

{  "authentications": {   "birstwebservice": {    "properties": {    "SOAP_ENDPOINT" : "https://url",    "USERNAME" : "myuser",    "PASSWORD" : "mypassword",    "REQUESTPARAMS" : {     "Content-Type" : "application/soap+xml;charset=utf-8",     "SOAPAction" : "http:///dataTransfer"     }     }   }  } }





HR_IMPORT_JSON


{ "REQUESTXML1": "<soap:Envelope xmlns:soap=\"http://www.w3.org/2003/05/soap-envelope\" xmlns:ins=\"insite:soapws:connectorn:v1\"> <soap:Header></soap:Header> <soap:Body> <ins:dataTransferRequestType> <ins:login> <username>${USERNAME}</username> <password>${PASSWORD}</password> </ins:login> <connector>Standard Worker</connector> <ins:download ins:dataFormat=\"csvCommaSeparated\" ins:dataEncoding=\"xml\"> </ins:download> </ins:dataTransferRequestType> </soap:Body> </soap:Envelope>", "SOAPACTION1": "http://dataTransfer", "REQUESTPARAMS1" : {"Content-Type" : "application/soap+xml;charset=utf-8", "SOAPAction" : "http://dataTransfer"}, "RESPONSEDATAPATH1": "Body.dataTransferResponseType.data.dataText.CDATA.ROW", "USERMAPPING1": "username:Field1,employeeid:Field1,customproperty2:Field4,firstname:Field5,lastname:Field6,secondaryEmail:Field7,title:Field8,customproperty3:Field9,customproperty12:Field13,departmentname:Field15,startdate:Field16,customproperty5:Field16,enddate:Field17,customproperty7:Field17,locationnumber:Field18,customproperty6:Field18,location:Field19,jobCode:Field20,secondaryPhone:Field21,middlename:Field22,companyname:Field23,employeeType:Field25", "RECONCILATIONFIELD": "username" }



Anand

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.