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