Apex Code Development You need to sign in to do that
Don't have an account?
PHP Toolkit works at first but then shows Invalid Session ID
I am trying to use the PHP Toolkit using the sample code provided here: http://wiki.developerforce.com/page/Getting_Started_with_the_Force.com_Toolkit_for_PHP
I am able to successfully connect and extract Lead information from my org, but then after a period of inactivity I get the exceptions below.
In my Session Settings I have "Lock sessions to the IP address from which they originated" checked but that hasn't made a difference.
Can anyone point me in the right direction?
EXCEPTION MESSAGES:
Exception INVALID_SESSION_ID: Invalid Session ID found in SessionHeader: Illegal Session. Session not found, missing session key: 00D500000006vB7!ARUAQFpriXMy7oaddw5052bEBuR5vtbCftB30aJvnhrZ3KctG7uCHtUV2QqV7qfUcCPeknpo6gskc4IgWUXlYW2iVat8Stvg
Last Request:
POST /services/Soap/c/29.0/00D500000006vB7/0DF50000000TRCW HTTP/1.1 Host: na3.salesforce.com Connection: Keep-Alive User-Agent: salesforce-toolkit-php/27.0 Accept-Encoding: gzip, deflate Content-Type: text/xml; charset=utf-8 SOAPAction: "" Content-Length: 774
00D500000006vB7!ARUAQFpriXMy7oaddw5052bEBuR5vtbCftB30aJvnhrZ3KctG7uCHtUV2QqV7qfUcCPeknpo6gskc4IgWUXlYW2iVat8StvgSELECT *******, ********, ********** from Lead WHERE Account__c IN (SELECT Id FROM Account WHERE ******** = '******') AND ************* = false LIMIT 20
Last Response:
HTTP/1.1 500 Server Error Date: Tue, 10 Dec 2013 18:04:34 GMT Content-Type: text/xml;charset=UTF-8 Content-Length: 1011
sf:INVALID_SESSION_IDINVALID_SESSION_ID: Invalid Session ID found in SessionHeader: Illegal Session. Session not found, missing session key: 00D500000006vB7!ARUAQFpriXMy7oaddw5052bEBuR5vtbCftB30aJvnhrZ3KctG7uCHtUV2QqV7qfUcCPeknpo6gskc4IgWUXlYW2iVat8StvgINVALID_SESSION_IDInvalid Session ID found in SessionHeader: Illegal Session. Session not found, missing session key: 00D500000006vB7!ARUAQFpriXMy7oaddw5052bEBuR5vtbCftB30aJvnhrZ3KctG7uCHtUV2QqV7qfUcCPeknpo6gskc4IgWUXlYW2iVat8Stvg
I am able to successfully connect and extract Lead information from my org, but then after a period of inactivity I get the exceptions below.
In my Session Settings I have "Lock sessions to the IP address from which they originated" checked but that hasn't made a difference.
Can anyone point me in the right direction?
EXCEPTION MESSAGES:
Exception INVALID_SESSION_ID: Invalid Session ID found in SessionHeader: Illegal Session. Session not found, missing session key: 00D500000006vB7!ARUAQFpriXMy7oaddw5052bEBuR5vtbCftB30aJvnhrZ3KctG7uCHtUV2QqV7qfUcCPeknpo6gskc4IgWUXlYW2iVat8Stvg
Last Request:
POST /services/Soap/c/29.0/00D500000006vB7/0DF50000000TRCW HTTP/1.1 Host: na3.salesforce.com Connection: Keep-Alive User-Agent: salesforce-toolkit-php/27.0 Accept-Encoding: gzip, deflate Content-Type: text/xml; charset=utf-8 SOAPAction: "" Content-Length: 774
00D500000006vB7!ARUAQFpriXMy7oaddw5052bEBuR5vtbCftB30aJvnhrZ3KctG7uCHtUV2QqV7qfUcCPeknpo6gskc4IgWUXlYW2iVat8StvgSELECT *******, ********, ********** from Lead WHERE Account__c IN (SELECT Id FROM Account WHERE ******** = '******') AND ************* = false LIMIT 20
Last Response:
HTTP/1.1 500 Server Error Date: Tue, 10 Dec 2013 18:04:34 GMT Content-Type: text/xml;charset=UTF-8 Content-Length: 1011
sf:INVALID_SESSION_IDINVALID_SESSION_ID: Invalid Session ID found in SessionHeader: Illegal Session. Session not found, missing session key: 00D500000006vB7!ARUAQFpriXMy7oaddw5052bEBuR5vtbCftB30aJvnhrZ3KctG7uCHtUV2QqV7qfUcCPeknpo6gskc4IgWUXlYW2iVat8StvgINVALID_SESSION_IDInvalid Session ID found in SessionHeader: Illegal Session. Session not found, missing session key: 00D500000006vB7!ARUAQFpriXMy7oaddw5052bEBuR5vtbCftB30aJvnhrZ3KctG7uCHtUV2QqV7qfUcCPeknpo6gskc4IgWUXlYW2iVat8Stvg
The "Lock sessions to the IP address from which they originated" param only takes care of the security aspect but doesn't extend the session validity :
Lock Session to the IP Address from which they originated
-This will force the user to only be able to log in from one machine at a time.
-This helps security by preventing the session ID to be used to log in from a different IP address, which could be an unauthorized attempt.
It might be that the session timeout value is less which is hit after some time of connection inactivity.