Synchronizing User Records

about user record synchronization the user record synchronization feature promotes a more consistent user experience by allowing users to retain their bookmarks and individual preferences regardless of which device they log in to user record synchronization relies on client server pairings the client is the device that users log in to start their remote access each client is associated with one primary server and one backup server to store user record data clients can be individual appliances or a node within a cluster a server in this instance is the device that stores the user data records each server can be configured to replicate its user record data to one or more peer servers servers are identified by a user defined logical name the same logical name can be assigned to more than one authentication server to let you associate authentication servers of different types to the same user for example, sa1 is an ace authentication server with user1 who creates a bookmark to www ivanti com sa2 is an active directory authentication server with the same user1 for the www ivanti com bookmark to be transferred from sa1/ace/user1 to sa2/ad/user1 you would assign the logical name "logical1" to both the ace server on sa1 and the active directory server on sa2 cluster vips cannot be used as the ip for synchronizing between clients and peers servers as long as the logical name is the same, the authentication servers can be different types and different server names and still be associated with a common user the username must be the same for user record data to be synchronized across the servers the logical authentication server (las) and username combination is what uniquely identifies a user record the following user records are synchronized between the client and server bookmarks web file terminal services jsam preferences persistent cookies cached passwords user session data is not synchronized persistent cookies, if changed, are synchronized when the user session terminates all other modifications to the user records are synchronized immediately user records are stored in cache on the client node prior to being pushed to the servers when a user logs in to a client, their data is pulled from the associated server the pull is performed in the background and does not delay the login process users using browsers that do not support javascript must manually refresh the index page for updated bookmarks and preferences to appear for browsers that support javascript, users may see a spinning progress indicator and their home page will refresh automatically with updated bookmarks and preferences clients and servers need not be installed with the same ivanti connect secure software version user record synchronization uses port 17425 this port number is not configurable if you are deploying across a firewall, configure your firewall to allow traffic on this port to set up user record synchronization, you perform the following tasks enable user record synchronization for each participating client and server, identify which ones are the client and which ones are the server and assign a node name to each client and server create a shared secret which is used to authenticate the client with the server and the server to its peer servers on each server, define which clients and peers are allowed to communicate with the server on each client, define the servers that handle records for each las server when enabling this feature, you have several options to initialize the user record database you can populate the database using user records located in the cache of the client systems populate the database using user records located in the cache of the server systems don't pre populate the database but populate it as users log in and out of the client system if you choose the last option, users may not be able to view their saved bookmarks and preferences until the next time they log in, depending on which client they log in to user records may not synchronize if the time clocks on the devices are not in sync we recommend that you use the same ntp server for each node participating in user record synchronization to keep system times accurately adjusted the user record synchronization feature will not start automatically after importing a system configuration that has this feature enabled the workaround is to disable user record synchronization and then enable user record synchronization from the user interface after the configuration import enabling user record synchronization the first step in enabling user record synchronizing is to define the node name and the shared secret used to authenticate between the clients and the servers select system > configuration > user record synchronization > general select the enable user record synchronization check box enter a unique node name this name is used when associating a client with a server and is different from the logical name assigned to a server this node name is also not the same as the cluster node name enter the shared secret and confirm it the shared secret is the password used to authenticate the client with its servers and the primary server with its peer servers use the same shared secret for all clients and servers participating in user record synchronization select whether this node is client only or if this node acts as both a client and server click save changes if you need to make any changes in this window at a later time, you must deselect the enable user record synchronization check box and click save changes make your edits, select the e nable user record synchronization check box and save your changes once you enter a name and shared secret, you cannot clear these fields configuring the user record synchronization authentication server to set up the authentication server you must define its logical name select authentication > auth servers click the name of the authentication server you want assign a las name by assigning the authentication server a las name, all users that authenticate using the authentication server are associated with this las in this instance, we are referring to the client nodes, not the user record synchronization server nodes select the user record synchronization check box enter a logical name to identify this server this allows you to share user record data across authentication servers on different devices by assigning a las name to an authentication server, you are implicitly assigning it to all users that authenticate with that auth server the combination of the user's login name and their las name uniquely identifies the user's user record across all user record synchronization servers click save changes configuring the user record synchronization server to set up the user record synchronization server you must define its peer nodes (optional) and the clients that can access this server select system > configuration > user record synchronization > this server enter the peer server's node name and ip address, then click add to specify more than one peer server, enter each server's node name and ip address individually and click add there is no limit on the number of peer servers you can add data is replicated from the primary or backup server to its peer servers if the primary is not available, user data is sent to the backup user data is then replicated to the peer servers for each client you want synchronized with this server, enter the client's name and ip address and click add once added, peer servers will have a colored icon next to their name indicating their connection status node status is provided to client nodes and las mapping servers as well color description green connecting yellow connecting gray not connected configuring the user record synchronization client to set up the client, you select the primary and backup server you want this client to synchronize with select system > configuration > user record synchronization > this client select the las name you want to synchronize and enter the primary ip of the user record if you prefer to synchronize with any available server, select any las enter the primary and optionally a backup server's ip address and then click add even if you select any las, you must enter a primary server ip address once added, the primary and backup servers have a colored icon next to their name indicating their connection status configuring the user record synchronization database with the database tab, you can delete inactive records from the client cache, retrieve statistics about the database, export and import the data and remove user data from the server's database to configure the database select s ystem > configuration > user record synchronization > database select auto delete inactive synchronized user records from the cache to remove inactive user records from the cache this option does not remove user records from the user record database when this option is selected, the system performs a check every 15 minutes and deletes user records that meet all of the following criteria there are no active user sessions associated with the user record the user record does not have any custom settings, or the latest version of the user record has been synchronized with the user record database the authentication server associated with the user record database does not have type "local" for example, the "system local" auth server that is part of the default configuration of the system has a "local" type, so any user records associated with that auth server will not be auto deleted however, user records associated with external authentication servers like radius or ldap may be deleted, depending on the two prior criteria select auto delete user records from the local synchronization database that have been idle for x d ays to permanently remove user records from the database located on the server enter the number of days user records must be inactive before being deleted in this instance, "inactive" means that no client has pulled the user record or pushed any modifications to the user record in x days click retrieve statistics to display the number of records in the database you cannot edit or view records in the database under export , you export user records to a file the user records can be exported from the user record database, or from the cache the exported file can be used to pre populate the user record database on another node enter the las name of the user records you want to export if you leave this field blank, all user records are exported if you enter a las name, only user records with the entered las name are exported to encrypt the exported data, select the encrypt the exported data with password check box and enter the password click export to export the user records from the specified source (cache or database) you will be prompted where to save the file under import, you import user records into the synchronization database the user records can be imported from a file or from the cache use the import operation to pre populate the user record database with user records exported from another node, or with user records from the cache click browse to locate the exported file and enter the password if the exported file was encrypted with a password select the override logical auth servers in imported user records with check box to replace the las name in each imported user record with the las name entered for example, you change the las name, use this option to update the user records with the new name click import under delete , specify which user records to permanently remove from the user record database the options you select apply only to the user record database associated with this server select user record with login name and logical auth server to remove a specific record the login name and las name together uniquely identify a user record select this option to remove that record (if it exists) select user records with logical auth server to delete all user records with the specified las name select all user records to permanently remove user records from the database on this node click delete scheduling user record synchronization backup you can configure periodic backups of the user record database user record synchronization backup can be enabled only on a user record synchronization server to back up the user record database ensure the system is set up as a user record synchronization server see system > configuration > user record synchronization select maintenance > archiving > archiving servers select the archive user record synchronization database check box specify an archive schedule through the options, schedule archives on any combination of weekdays including weekends if you schedule an archival operation to occur during the hour that your system switches to daylight savings time (dst) the operation may not occur as scheduled for example, if your system is set to change to dst at 1 00 a m and you have scheduled an archival operation to occur at any time between 1 01 a m and 1 59 a m , the operation is not accomplished, because at 1 00 a m the system clock is moved forward to 2 00 a m and the system never reaches your archival time for that date define a specific time when you want the system to archive data or elect to archive data every hour, which produces twenty four files with unique timestamps we recommend you schedule an archival operation during hours when traffic is light in order to minimize its impact to your users the automatic archiving process compresses files and, if the system is busy, can degrade performance for users also, a cluster node may appear unresponsive if the system is busy with traffic and performing archiving simultaneously provide a password if you want to encrypt user record synchronization database archives with a password (optional) click save changes