NOTE: Ubisecure product names were unified in autumn 2011. All products which started with term "Ubilogin" were renamed to start with term "Ubisecure". In documentation this name change is implemented retroactively, i.e., the new naming practice is used also when referring to old software versions which started with term "Ubilogin" at the time of their release.

This documentation describes the SQL specific implementation alternative for the Ubisecure External Directory Integration feature. The main focus is on the installation and configuration of this alternative of the Ubisecure External Directory Integration feature.

This alternative can be used with any SQL-based user database. In Ubisecure terminology, the chosen database is also called the External Directory.

In this case the Ubisecure Authentication Server has a JDBC connection with the external directory.


Figure 1. Ubisecure SQL Integration architecture overview

Requirements

For successful integration, the following conditions should be met:

Ubisecure SSO Server is accessible with administrative privileges
Ubisecure SSO Server version 5.0.3 or greater
SQL database tables or views for Ubisecure SSO. Ubisecure SSO requires the following SQL tables: UbiloginAccountStatus, UbiloginPassword and UbiloginAttributes. The attributes in the SQL tables are further documented in the SQL Accounts document.
SQL database connection credentials with read/write access to the SQL tables or views
JDBC driver files for the database system you are using
Ubisecure Management installation directory is accessible

Browser not supported