C L Groth 15.May.02 04:37 PM a Web browser Sametime Developers Toolkit 2.0 Windows NT/2000
We have an application that uses the sametime_token to sign into the LiveNamesApplet using the "SametimePreWebQueryOpen" and "SametimeWebQueryOpen" agents. It works wonderfully on one iSeries production server. The web application is on one server in the domain and the Sametime server is also in the domain.
However, we have the exact copy of the database on another server and we cannot sign in. We receive "Unable to access sametime due to incorrect login" message.
The test server is a sametime server. We are running SSO in both environments. The production server is running SSL, while the test environment is not. The SSO expiration is 30 minutes.
Since the applets are exactly the same, I am wondering if it is an issue with the sametime token. If I display the sametime_token field on the test environment, it is always the same, whether I come back in 30 minutes,8 hours, or the next day.
My question is, where is this token stored? In the browser? On the server? And how do I clear it out to get a new one?
If another user logs in, they continually receive their personal same token each time as well.