Publishing security data

The following section describes how to publish the security data associated with the main iBase database. Before you can configure the Publisher for a security database, the iBase administrator should have already set up the iBase security database on the server that is the Publisher.

Before you begin

If you intend to replicate the security audit log, include the _ AuditLog table when you create the publication.

Note: In iBase, this database is typically referred to as the security file.


To create a publication for security data:
  1. From the Object Explorer list, select Replication > Local Publications, right-click and select New Publication.
    • Server: select the server that is also the Publisher of the entity and link data for the iBase system. (Use the same server for all publications.)
  2. On the Publication Database page, select the existing database that contains the security data you want to publish.
    The database name is <database>_Sec where <database> is derived from the name of the ids file created at the publisher site.
  3. On the Publication Type page, select Merge publication.
  4. On the Subscriber Types page, ensure that only SQL Server 2008 or later is selected.
  5. On the Articles page, expand the Tables node. Select these iBase system tables:
    • _ AccessDenied
    • _ AuditLog (omit this table if you do not want to replicate the security audit log)
    • _AutoLogon (optional but only relevant if Windows Single Sign-On is used and users are able to log on to the different systems using the same Windows credentials)
    • _CommandGroup
    • _Group
    • _PasswordHistory
    • _SecurityPolicy (optional)
    • _User
    • _ UserGroup
    • _UserSettings
    You must not include these tables:
    • _Configuration_Binary
    • _Configuration_Def
    • _Configuration_Text
    • _ NextId
  6. Accept whatever article issues are reported - typically SQL Server warns that “Uniqueidentifier columns will be added to tables”.
  7. Enter the publication name. For example, iBase_security_data.
  8. Generate the publication in the usual way. There are no additional properties to set for this type of publication.

What to do next

After you create the publication:

  1. Restrict access to the tables in the SQL Server database. See the Administration Center document Managing Access Control, for details.
  2. Back up the database(s). See:
    • The Administration Center document Creating and Maintaining Databases, for information on backing up iBase connection files
    • Microsoft SQL Server documentation for information on backing up the replicated SQL Server databases
  3. Tell the iBase administrator that the security data at the Publisher is configured for replication.