+ Start a Discussion
JBabuJBabu 

Session ID life in integration

Hi,

 

Third party system connects to Salesforce via login - user name and pwd and it gets session id and server url.

 

There are multiple servers at third party system.

 

First server connects to Salesforce via user name and password and Saleforce sends session id and server url.

As per the load balancing now server 2 connects to Salesforce instead of server 1.

In this case does Salesforce sends same session id and server url (i.e., when server 1 was connected) when server 2 connects to Salesforce or session id and server url would be different.

 

Please let me know the details.

 

Thanks,

Babu.

Best Answer chosen by Admin (Salesforce Developers) 
Bhawani SharmaBhawani Sharma
If your second server again calling the login api, then yes. new session id will be get created.
but if your second server using the same session id which was retrieved from first server, then it is also okay as long as session id is valid.

All Answers

Bhawani SharmaBhawani Sharma
If your second server again calling the login api, then yes. new session id will be get created.
but if your second server using the same session id which was retrieved from first server, then it is also okay as long as session id is valid.
This was selected as the best answer
JBabuJBabu
2nd server does not get session id from server 1. So as per your response 2nd server would get a new session id Thank you..
Jerun JoseJerun Jose
Yes. SFDC support parallel sessions and the session IDs will remain valid unless they are not used for a particular time limit. This session timeout can be setup at the org-level in SFDC