SLLauncher no longer launches SLBroker with NSL6.1

  • 3384549
  • 21-Feb-2008
  • 26-Apr-2012



Customer does not want any NSL modules to run on their Citrix server until specifically called by SLLanucher.
Customer wants to use SLLauncher for Citrix published applications exactly as it did in prior versions.

Unfortunately, with NSL6.1 SLLauncher no long launches SLBroker as it did in prior versions, and unless the default NSL modules are allowed to run, single-sign-on into published applications will not occur.


The old SLLauncher method will work fine, but customers need to allow SLWTS to run.

SecureLogin handles single-sign-on into Citrix published applications differently in NSL6.1 than it did in prior versions. With SecureLogin 6.1 a new component, SLWts.exe, is installed that allows SecureLogin to handle Citrix published applications automatically. This is in comparison to previous releases, where users manually configured published application shortcuts via SLLauncher. With 6.1 no SLWTS.exe related configuration is required. Citrix published applications will be SSO-enabled automatically.

If you upgrade from a previous version of SecureLogin SSO, you are not required to change any SLLauncher.exe shortcuts previously created for published Citrix applications. Once installed, SecureLogin SSO modifies the existing SLLauncher.exe automatically, so that it is simply a shell that will run any command line passed to it.

The new SLWTS component will also launch for published desktop or other logins (including RDP only) which will allow SSO to be available before the users desktop and applications actually start.

Because it is implemented as a Citrix identified service, SLwts will not hold the Citrix session open when the published application is closed – Citrix will end