[Vipassana] - It is seeing the reality as it is, And not as you want it to be.!!!
SCJP1.5.
Pravin Shirke wrote:Hi Manish,
I suggest you keep a flag in your user maintenance table, with default value as 'N'. (i.e. not logged in) and once you login successfully into the application update the flag as logged in (some flagging value like 'Y') and every time you try to login to the application for a particular user just check that the value of the flag is 'N' if it is 'Y' redirect to login page and failed the login process with appropriate message for the user. This will work irrespective of machine the user has logged i.e. it will ensure that only once session exists for a user.
Hope this helps...
SCJP
Amreen Bhatti wrote:Set the session ID in the SOAP header so that the API can validate subsequent requests for this session.
Specify the server URL as the target for subsequent service requests. You must change to the server URL, the login server only supports login calls
SCJP
Amreen Bhatti wrote:Set the session ID in the SOAP header
[Vipassana] - It is seeing the reality as it is, And not as you want it to be.!!!
SCJP1.5.
Pravin Shirke wrote:Hi Sourabh,
For implementation of resetting the flag to 'N' once the user closes the browser window, you need to invoke javascript function like:
Assuming, you have set the session id in context, then the listener would do the rest as its SessionDestroyed() method would be called; wherein you need to invoke DB call for the particular user to reset the flag to 'N'.
SCJP
ya but the process would fail if the scripts are turned off.....
[Vipassana] - It is seeing the reality as it is, And not as you want it to be.!!!
SCJP1.5.