-
July 2nd, 2015, 09:26 AM
#1
Hi Dejan,
I confirm you that following a reconnection the sessionId is replaced and that a new sessionId is involved for each new try.
In this case, when the reconnection succeed your Metadata Adapter will receive a new authentication request (Notify User) with the user password parameter set with the old token.
Now, if you handle the token as a "one time password" your Metadatata Adapter will not authenticate the user and the reconnection will fail.
Now you could consider two alternatives:
- give up the automatic reconnection mechanism that provides the JavaScript client library, and after each disconnection restart with the procedure of sending credentials;
- provide your token a wider validity, considering the "user/token" combination validfor a certain period of time, for example a few hours or a day.
Please let us know if you need any further clarifications.
Regards,
Giusppe
Similar Threads
-
By LS_Developer in forum Client SDKs
Replies: 7
Last Post: June 14th, 2012, 08:35 AM
-
By emiliob in forum Client SDKs
Replies: 12
Last Post: October 14th, 2010, 07:00 AM
-
By k0nan in forum Adapter SDKs
Replies: 1
Last Post: May 12th, 2010, 09:50 AM
-
By cbcrack in forum Adapter SDKs
Replies: 3
Last Post: January 7th, 2008, 09:07 AM
-
By Alessandro in forum Adapter SDKs
Replies: 2
Last Post: July 30th, 2007, 11:29 AM
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 11:53 PM.
Bookmarks