Skip to main content
Find a Sales Rep

Keyscan Auora Community Integration - Keys are not synching

Updated

Why are keys created in Community not syncing with Aurora/Keyscan?

  • Verify that the Aurora Server address configured in Community is correct (IP address or localhost, as applicable). In Advanced Settings > Enable AuroraSync Interface, click Test Connection and confirm that the test returns a successful connectivity response.
  • Ensure the following services are running. If any service is stopped, start it:
    • Keyscan Aurora Agent
    • Keyscan Aurora Communications
    • Community AuroraSync
  • Verify the number of groups configured in Aurora. Aurora must contain 10 groups or fewer.
  • Confirm the username and password configured in the Aurora Interface section of Community:
    • The account must have Master access in Aurora.
    • Log in directly to Aurora using this account to confirm the credentials.
    • If the password was recently created or changed, logging into Aurora completes activation. The account is not valid until this login occurs.
    • An incorrect password may still return a false-positive result during connection testing.

  • Confirm that two Common Area Access groups exist in Community:

    • Resident Common
    • Staff Common

    The corresponding Keyscan groups must be visible within these Community groups and set to Auto or Selectable, as required. Also verify that all keys are selected in the adjacent Credentials tab.

    Note that Aurora supports a maximum of two concurrent user sessions. Community counts as one active user session.

Additional Information

If the Community Server and the Aurora Server are installed on separate machines, configure the firewall on the Aurora Server to allow the following inbound ports:

  • 27702 — TCP/IP
  • 8740 — TCP/IP
  • 3001 — TCP/IP
  • 9999 — TCP/IP
  • 6000 — TCP/IP
  • 6001 — TCP/IP
  • 1434 — UDP

  • Aurora SQL TCP dynamic port
    To determine the SQL dynamic port, open the Windows Run or Search box and enter:

    • SQLServerManager11.msc (Aurora 1.0.21.0 or earlier)
    • SQLServerManager14.msc (Aurora 1.0.22.0 or later)

    In SQL Server Configuration Manager:

    1. Expand SQL Server Network Configuration.
    2. Select Protocols for AURORA, and open TCP/IP. 
    3. On the IP Addresses tab, scroll to IP All and note the value for TCP Dynamic Ports.

Applies To

Community with Aurora / Keyscan integration

Related to