Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.
The customer has deactivated SecureLogin by right clicking on the icon in the system tray and toggling the Active menu item. It is definitely not active.
However, when the customer runs terminal emulators configured with SecureLoginâs Terminal Launcher, they still SSO to applications even though SSO should be inactive. All other applications can be completely deactivated in this manner.
In versions of SecureLogin earlier than v3.5, anytime TLaunch.Exe runs, it ignores whether SecureLogin is active or not. Deactivating SecureLogin will not deactivate Terminal Emulators that have been SSO enabled using Terminal Launcher.
You must run your emulator natively (bypass Terminal Launcher) if you donât want to SSO to the emulator.
This issue is resolved in version 3.5. Deactivating SecureLogin will also deactivate SSO to terminal emulators.