Prevening a single point of failure for SecureLogin

  • 7940390
  • 19-Aug-2009
  • 26-Apr-2012


Novell SecureLogin 6.0
Novell SecureLogin 6.1


Preventing a single point of failure for SecureLogin


Novell SecureLogin (NSL) is not linked to any single point of failure. The solution runs on top of any mature, proven, and stable data store.  Since all data is stored within the data store (eDirectory, Active Directory, LDAP, etc.); NSL leverages the built in fault tolerance and service resolution (e.g. SLP / DNS ) of the data store and any existing backups, security, and management of the environment. For example, if it cannot locate one replica holder / domain controller for some reason (i.e. system down), NSL will contact another replica / domain controller to access SSO data stored against the user object.

If the entire directory (including all replicas/partitions) fail, SecureLogin switches to the offline cache (if enabled).  When the Directory comes back online, a synchronization occurs between the Directory and the offline cache and time stamps determine which data (e.g. credentials that may have changed) is most recent.