CmapServer v5.05 - Release January 24, 2014

• Cmaps with header and footer information will not display correctly in HTML when retrieved from a CmapServer. Exporting to HTML works fine.
• On very rare ocassions, creating a folder in a CmapServer will give an error. The folder will be created but is not displayed in the Views until the CmapServer is restarted, and the user can therefore not use it until the CmapServer is restarted.

CmapServer v5.04 - Release July 16, 2010

• The option to send the author an email with the userid and password authentication information for a folder does not always work (fixed in v5.04.03)
• On a CmapServer with LDAP authentication, searching for users in the LDAP directory may cause too many entries to be returned, resulting in an error message "Problem communicating with user directory". The suggested workaround is to use a more specific search query which matches fewer entries.
• On very rare ocassions, a CmapServer will not register with the Directory of Places (DOP) (fixed in v5.04.01)
• A Snow Leopart update on the Mac updates the Java 1.6 to update 20. This has generated an incompatibility that makes results in the log files being truncated shortly after the program launches. The execution of the program is not affected but the log files will be incomplete (fixed in v5.04.01)

CmapServer 5.03.03 - October 15, 2009

• On a server with more than one ethernet port, if the CmapServer is configured to bind to one port in particular, the http-sockets protocol (which is used if port 4447 or whatever is used to communicate between client and server is not accessible) will fail (fixed in v5.04).
• A Snow Leopart update on the Mac updates the Java 1.6 to update 20. This has generated an incompatibility that makes results in the log files being truncated shortly after the program launches. The execution of the program is not affected but the log files will be incomplete.
• On a CmapServer with LDAP authentication, searching for users in the LDAP directory may cause too many entries to be returned, resulting in an error message "Problem communicating with user directory". The suggested workaround is to use a more specific search query which matches fewer entries.

CmapServer 5.03.01 - June 5, 2009

• This CmapServer distribution contains a bad webserver (Tomcat) configuration file (web.xml). It is recommended that you update to CmapServer v5.03.03. To do so, shutdown your CmapServer and run Check for Updates.

CmapServer v5.03 - May 19, 2009

• The panel to specify the CA’ certificate from a file when you install a CmapServer in console mode never show up, the installer simply skipped this panel and so you couldn't specify the CA’ certificate from a file.
• When you are installing a CmapServer and select the CmapServer connection mode: SSL, the panel to specify the SSL keystore and SSL keystore password never show up, the installer simply skips this panel and you cannot specify these parameters.

CmapServer v4.18 June 09, 2008

• At this time we don't have Known Issues for this version

Note: CmapServer v4.17 was an internal version that was not publicly released.

CmapServer v4.16 - March 11, 2007

• Internet Explorer is not able to handle the "no-cache" parameter of the CmapServer's servlet.

Note: CmapServer v4.15 was an internal version that was not publicly released.

CmapServer v4.14 January 10, 2008

• The LDAP implementation of the CmapServer does not allow a null value for the groupBaseDN parameter, since it is required by LDAPUserDirectory.

Note: CmapServer v4.13 was an internal version that was not publicly released.

CmapServer v4.12 . October 18, 2007

• Even if a user has "Administrator" privileges over server "B" and admin privileges over a folder stored in server "A" prior to doing a "Copy to Folder with permissions" action using that folder from server A to a destination on server B where the "Everyone" user has "Add folder" permissions, if the folder contains at least one Cmap, resource, or folder, then the user will still be prompted for credentials to write the source folder's contents into the destination folder.
• Trying to supply a '\' in the User ID when attempting to authenticate using a pre-Windows 2000 naming convention in an LDAP-enabled CmapServer that has been configured to use an Active Directory LDAP server will yield an error dialog that says there was a problem communicating with the user directory.
• The AdminTool's IndexChangeService settings behave unexpectedly.
• When installing over an existing CmapServer, the string for the option to choose both Standard and LDAP permission schemes reads "Standard LDAP" instead of the expected string "Standard + LDAP".
• The title of the webpage when browsing a CmapServer's index and its folders appears as the string "IHMC CmapServer v4.10" instead of the expected string "IHMC CmapServer v4.11".
• Under certain circumstances, the License Agreement, the Ceryph notification, or the first screen in the CmapServer installer may appear blank.
• Text in the installer is misaligned and some of text is missing on the Administrator ID/password screen.

CmapServer v4.11 – July 06, 2007

• Even if a user has “Administrator” privileges over server “B” and admin privileges over a folder stored in server “A” prior to doing a “Copy to Folder with permissions” action using that folder from server A to a destination on server B where the “Everyone” user has “Add folder” permissions, if the folder contains at least one Cmap, resource, or folder, then the user will still be prompted for credentials to write the source folder’s contents into the destination folder.
• Trying to supply a ‘\’ in the User ID when attempting to authenticate using a pre-Windows 2000 naming convention in an LDAP-enabled CmapServer that has been configured to use an Active Directory LDAP server will yield an error dialog that says there was a problem communicating with the user directory.
• The AdminTool’s IndexChangeService settings behave unexpectedly.

CmapServer v4.10 – May 09, 2007

• When performing a “reinstall” of the v4.10 CmapServer on top of an existing installation of the CmapServer on Windows, it may be possible in some situations for the new “serverconfig.txt” and “slp.conf” files to disappear after rebooting the machine.  For this reason, it is recommended that if backup copies of these files have not already been created prior to doing a reinstall, the server admin should manually make a copy of both files and replace the “txt” and “conf” extensions with “bkp”.  That way, if the problem does occur due to an automatic reboot of the machine and the CmapServer’s “service” is set for “Automatic”, then the CmapServer will automatically try to use the *.bkp versions of the two files if they are missing upon launch.
• The “Select Soup to Join” search window will successfully locate Soups from the servers listed in My Places, but unexpected soup search results may occur for soups stored in CmapServers which do not register with the IndexServer.

CmapServer v4.09 – January 02, 2007

• When clients older than CmapTools v4.08 attempt to add folders and resources using standard permissions on a CmapServer configured to only use LDAP permissions, they will be able to do so as if the CmapServer were setup to use both LDAP and standard permissions (“both” configuration; also known as “mixed” mode).
• When clicking a resource link or a shortcut to a Cmap or resource stored in a folder that is either no longer present in it's original location or no longer exists at the time the resource link was made, the CmapServer will prompt the user for a User ID and Password that they will never be able to bypass with any credentials.  Subsequently when a user tries to access a URL to the web version of an absent folder the web servlet will prompt them for credentials in the same manner as in CmapTools and as they click cancel they will receive a 401 error message.  For URLs that point to any of the contents of the absent folder they will receive a 500 error.
• If a server admin decides to make use of audit mode and adjusts the audit mode configuration during installation of the CmapServer, the serverconfig.txt file will not reflect the audit mode configuration supplied during installation.
• The server has several issues with installing and running correctly on Windows Vista.
• When attempting to view the Web version of a Cmap or resource stored in a locked-down folder in a Place on Mac OS X, Safari will not prompt the user for credentials and will instead report that the access is “Unauthorized”.

 CmapServer v4.08 – November 30, 2006