Does SecureLogin Single Sign-On replace the Microsoft client GINA?
SecureLogin installed in AD mode.
SecureLogin Single Sign-On does not replace the Microsoft GINA. Users still logon to the LAN exactly the same as before SecureLogin Single Sign-On was installed (Active Directory password, for example). Once the user is authenticated to the LAN, SecureLogin starts up and retrieves and enters application passwords on behalf of the user.
SecureLogin does not change the Microsoft GINA or your backend applications in any way, and does not require modules on your application servers. By simply deactivating SecureLogin via the system tray icon (if the SSO administrator allows them), the client (e.g. Windows 2000, XP) operates exactly as it did before SecureLogin was installed.