1 _________________________________________________________________ Release Notes: InfoBroker Server Version 2.1A for Digital UNIX The following section descibes the bugs fixed since version 2.1 of InfoBroker and delivered in the MUP kit V2.1A. 1.1 Bugs fixed in the MUP release 2.1A o Image files displayed by the lookup daemon must be located in this directory: /var/ibx/lookup/ o For searches with more than one match, the lookup daemon used to display only the X.500 distinguished name, which was not enough information in most cases. Now, for the case of multiple matches, the lookup daemon displays each attribute marked with a T in the brief column in the configuration file (/etc/ibx.conf). o The lookup daemon did not properly format rfc822 mailbox address attribute values. This caused the display to appear jumbled when viewed with a Netscape Version 2 browser. This is resolved. o The lookup daemon did not properly display brackets and percent characters (<, > and %) in rfc822 mailbox attribute values. This is resolved. o The installation of the IBXOSERV subset now properly checks for either Version 2 or 3 of the X.500 base kit as a prerequisite. Previously it checked only for Version 2 of the X.500 base kit. Release Notes: InfoBroker Server Version 2.1A for Digital UNIX 1-1 Release Notes: InfoBroker Server Version 2.1A for Digital UNIX 2.1 Server Release Notes The following sections contain release notes for the InfoBroker Server V2.1A. 2.1 Server Release Notes o The InfoBroker Server supports all variations of Versions 1 and 2 of the LDAP protocol. o The InfoBroker Server supports the following LDAP functions: bind, search, add, modify, modifyrdn, delete, unbind. o The Version 2.1 installation process saves your Version 1.n oidtable.* files in /var/ibx. If you customized your schema for the InfoBroker Version 1.0 or 1.0A server, you can find your customized oidtable.* files in /var/ibx. To customize the schema for the InfoBroker Version 2.1, edit the .sc files using information from the oidtable.* files as a guide. See the InfoBroker Server Administration Guide for more information regarding customizing your schema. o When a server is already running on the system, the InfoBroker startup command falsely reports having started a second server daemon. If you attempt to start the InfoBroker server when one is already running on the system, the startup procedure will not detect this and will falsely indicate that the server has started. If you check the /var/ibx/ibx.log file, you will see the following entry at the end of the file: Release Notes: InfoBroker Server Version 2.1A for Digital UNIX 1-2 Release Notes: InfoBroker Server Version 2.1A for Digital UNIX 2.1 Server Release Notes Digital Equipment Corporation InfoBroker Server v2.1 (Thu Jan 12 13:54:04 EDT 1995) Began execution on Tue Feb 28 12:44:36 1995 Using X.500 Not able to connect on TCP Not able to listen on DECnet for LDAP Not able to listen on DECnet for DMW Not able to connect on TCP The 4 lines at the end indicate that the server was unable to listen on any of its ports, due to the server that is already running. o If you specify a NULL string as the search-base argument, the InfoBroker starts searching at the top of the directory tree. o The InfoBroker falsely reports the status of searches that exceed the time limit. A search request that exceeds the time limit before any matches are discovered returns LDAP_NO_SUCH_OBJECT, rather than LDAP_TIMELIMIT_EXCEEDED. If the X.500 DSA finds matching entries before the time limit is exceeded, the matching entries are returned along with the LDAP_TIMELIMIT_EXCEEDED error. 2.2 Client API Library Release Notes o The InfoBroker Client API Library attempts to bind using V2 of the LDAP protocol. If the bind fails for any reason, the client API library attempts to re-bind using V1. It attempts the re-bind transparently to the calling application. o When writing LDAP-compliant client code that modifies a single-valued attribute, use the replace parameter of the LDAP modify function. You cannot modify a single-valued attribute by deleting the old value and adding the new value in a single step, unless your client application uses the replace parameter of the LDAP modify function. Release Notes: InfoBroker Server Version 2.1A for Digital UNIX 1-3 Release Notes: InfoBroker Server Version 2.1A for Digital UNIX 2.3 MailWorks Release Notes 2.3 MailWorks Release Notes o If you use the InfoBroker Server Version 2.1 with a version of MailWorks previous to MailWorks Version 1.5, then you must edit the /usr/opt/MAILworksrc file. If you use the InfoBroker Server Version 2.1 with a version of MailWorks previous to MailWorks Version 1.5, then you must perform the following edits to the /usr /opt/MAILworksrc file: - If running TCP/IP, change DAXportid from 389 to 3883. - If running DECnet, change DAXportid from LDAP_SERVER to DMW_LDAP_SERVER. 2.4 X.500 Release Notes o The X.500 dxim utility may generate invalid workgroup- directory entries. A workgroup-directory file that attempts to assign a list of values to an attribute must surround those values with a pair of parentheses, as follows: create entry /c=us/o=companyname/ou=engineering/cn="Albert Einstein" - commonName=("Al", "Albert E.", "Al Einstein") If you use dxim to generate a workgroup-directory file using the select and show select commands, it produces the following syntax, which is not valid for use with the InfoBroker server: create entry /c=us/o=companyname/ou=engineering/cn="Albert Einstein" - commonName= """Al"", ""Albert E."", ""Al Einstein""" Release Notes: InfoBroker Server Version 2.1A for Digital UNIX 1-4