Ultra Light Client Guide and Reference

ULC Reconnect Token Strategy

The ULC client reconnect feature assigns a token to each context. This token is used during reconnect to find the contexts. Normally these are the contexts which belong to the user who just tries to reconnect. Therefore this token is normally a unique identifier for a user (i.e. user ID). However the token can also contain other information such as an application name.

Every client reconnect token strategy must be a subclass of the abstract class UlcReconnectTokenStrategy and is responsible for creating and handling the token of a context. It is up to the (infrastructure) programmer to implement such a strategy. A company would normally use one single strategy for all ULC applications. Specific strategies can be implemented for administrative and maintenance purposes (e.g. a strategy that allows a super user to reconnect to any hanging context).

The following strategies are included in this release for demonstration and debugging purposes only. They should not be used in production code.

UlcUserPasswordTokenStrategy
This is an example of the common use case where the context token is a unique user ID. This strategy asks the user for name and password. Because user interaction is involved, this strategy also has a UI proxy which handles the user input and encrypts it for minimal security using a challenge string.
Note:
Even though user name and password are encrypted using a challenge string sent to the UI, this is not very safe since byte codes can easily be re-engineered. Therefore you should only use this strategy if the connection itself is secure (e.g. SSL).

UlcShowAllTokenStrategy
This strategy is an example that shows how every user can be allowed to reconnect to any hanging context.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]