We currently use .2xa files created on demand to supply user credentials to our customers for unique user accounts. Currently the pool is 500 users. A web service delivers the usernames to the local launcher application (built in house), which then builds a custom 2xa file that is called. Unfortunately after the user ends their session the user information is cached into the local install of the 2x client. This causes a problem when a user just opens 2X on the task bar and launches the published application directly instead of using our own Launcher. By the time the user does this, we have seen occasions where the previously supplied account is now in use legitimately by another client. I know they are launching directly out of the 2x client because those entries show up in the log file as application #22 as opposed to the text name of the application that the 2xa file calls. Is there any way to prevent the caching of user credentials supplied by a .2xa file into the local install of the 2X Client?
