How is SecureLogin centrally managed?

  • 7940667
  • 19-Aug-2009
  • 30-Jan-2014


SecureLogin SSO



How is SecureLogin centrally managed?



SecureLogin preferences and Single Sign-on enabled applications and password policies are centrally managed using existing Directory management tools. For example, the Microsoft Management Console (MMC) is used to administer SecureLogin in a Microsoft Active Directory environment and iManager is used in a Novell eDirectory environment.

Changes can be made and new applications can be Single Sign-on enabled for all users through the power of the Directory, providing complete control over the Single Sign-on environment, even after the client has been deployed. Administrators can assign Single Sign-on enabled applications and settings to User objects, Organizational Units, Containers and via Group Policies.

Options such as which applications are enabled/disabled, whether the user is enabled/disabled, whether they have access to an offline encrypted cache for disconnected mode, whether the icon is displayed in the system tray, and whether they have access to Single Sign-on enable their own applications, can all be configured centrally with a few clicks of the mouse.

Other solutions often include a number of proprietary management utilities that support staff must learn and use to deploy and manage the Single Sign-on environment. The management capabilities of SecureLogin are far superior, with many more options and features.