How to force Spotfire Server to not switch to port 389 for looking up domain names when using a global catalog.

How to force Spotfire Server to not switch to port 389 for looking up domain names when using a global catalog.

Product: TIBCO Spotfire Server Version: 6.x or newer OS: All Supported Operating Systems -------------------- Spotfire Server uses port 389 to lookup domain names even though the LDAP configuration is set to use a global catalog. The reason the Spotfire Server is connecting to port 389 is that the Spotfire Server needs to perform look ups in the RootDSE on the AD server. The Global Catalog only contains a small number of attributes and may not return all information needed for the Spotfire Server to correctly handle the domains. More specifically, the Spotfire Server needs to examine the configurationNamingContext of the RootDSE to determine domain information. Forcing Spotfire to not look for domain information in the RootDSE via port 389 could lead to missing domain name mappings, which will then need to be added manually. See KB 43433 for details on how to do this. Note that if you force Spotfire to not lookup domain names on port 389 when using the global catalog, you will need to manually add domain name mappings to the Spotfire server configuration (See KB 43433). There is a setting that can be added to the configuration XML. One can add false under the part. 1). Export the current configuration from the Spotfire server (See KB 42941). 2). Open the exported configuration in a text editor. 3). Search for . 4). Add false just beneath . 5). Save the configuration file. 6). Import the configuration to the Spotfire database (See KB 42942). 7). Restart the Spotfire server.