Which Applications can SecureLogin Single Sign-On enable?

  • 7940160
  • 19-Aug-2009
  • 08-Jan-2014

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.


SecureLogin SSO
All Versions
MS AD, LDAP, NT4, Citrix, Terminal Services



Which Applications can SecureLogin Single Sign-On enable?



Due to the fact that SecureLogin doesn’t change application servers or require modifications to applications, it can SSO enable applications developed in any language and running on virtually any system or backend server. It literally doesn’t matter whether the application backend is a UNIX box, Windows server or IBM Mainframe (or any other system).

The type of applications supported includes but is not limited to both off the shelf and in-house developed applications developed in or running on;

  • VB,
  • C++,
  • Java,
  • Oracle,
  • Windows 32-bit,
  • Web (Intranet and Internet),
  • Finance Systems such as SAP, Oracle Financials, Bloomberg etc.
  • Helpdesk Systems such as Remedy, PeopleSoft etc.
  • e-mail systems such as Lotus Notes, Groupwise and Microsoft Outlook, Hotmail, Yahoo
  • Terminal Emulators such as Eicon Aviva, IBM Personal Communicator, Attachmate Extra, WRQ Reflections etc. connecting to UNIX, Mainframes and other host systems

A true SSO solution must be able to handle more than just logon. If it doesn’t, users will have to contact the Helpdesk with issues resulting from password changes, account locked etc. and it will cause more trouble than it is worth. E.g. if a password changes and SSO doesn’t handle it, how will the user know their old password (they haven’t entered it for days and possibly months)?

What you must do to fully SSO enable depends on what events the application triggers (e.g. password expiry) and what messages it displays (e.g. invalid logon).

  • Logon
  • Invalid Username
  • Invalid Password
  • Account Locked
  • Password expiry
  • Password change invoked by the user (e.g. Tools>Change Password)
  • Password policy
  • Password history (e.g. new password the same as the old)
  • Any other messages an application produces (e.g. SecureLogin can read an otherwise meaningless error such as e102r and can be used to produce user friendly messages or even resolve the problem without user intervention).

To SSO enable any application, the wizard or predefined applications can be used and/or a created.

NOTE: Applications only need to be SSO enabled once and can be published to everyone in the Directory centrally with a few clicks of the mouse.