You need to sign in to do that
Don't have an account?
michaelforce
Identity Confirmation / S-control Conflict ??
I have been seeing some strange problems pop up all around our org, and they all seem to support a theory I have developed which goes like so:
If a user is logging in from an IP address that is NOT on the whitelist, they are asked to activate the computer. Once the machine is activated, they can then log in and use the application. The user, however, will not be able to correctly display / utilize s-controls which make use of the AJAX toolkit. The soap messages are not accepted by the API and it seems that the error returned is that of 'invalid session ID'.
Several users have reported s-controls not working, and upon adding them to the whitelist they began to work again. I imagine that this would be a problem experienced by many customers by now... has anyone seen problems?
An SControl, or any other API client doesn't know about cookies. What this means is that the scontrol or other API client needs to login with username and password+token.
Now, if you are getting your session id from the service and are not executing a login, then it should work properly. If not, then Houston, we have a bug.
As you said, the s-control is ignorant to cookies... unless you tell it to search for and read the cookie. Perhaps there is information within it that would help us as part of a workaround. Although I would anticipate that such a workaround would also require modification of the toolkit.