fighting for truth, justice, and a kick-butt lotus notes experience.

IBM Notes Traveler 8.5.3. UP2 IF2 may break Directory Lookup

 April 23 2013 10:23:14 AM
Two customers called me this morning regarding issues with the Directory Lookup, which did no longer work after installing the Interims Fix 2 for IBM Notes Traveler 8.5.3 Upgrade Pack 2.

The Interims Fix 2 contains a fix regarding the directory lookup, which will change the default behaviour:
LO74676 Server Honor ACL control by default for Corporate Look up.

With this Fix the Notes Traveler server was updated to enable ACL check by default for corporate lookup:
The current behaviour is that when Notes Traveler does a look up names from the device will find all of the fields even if reader fields have been defined. As work around can be done to set the notes,ini parameter NTS_LOOKUP_ENFORCE_ACL=1 to have Notes Traveler honor the reader fields in the names.nsf file.

This APAR will change the default behaviour to honor reader fields by default.

As you can see this was already possible in the past using the notes.ini entry NTS_LOOKUP_ENFORCE_ACL. But the setting was off by default.

If you take a look at your Traveler configuration using

tell traveler config

You should find this setting in the list:

Image:IBM Notes Traveler 8.5.3. UP2 IF2 may break Directory Lookup

After IF2 this is on by default (NTS_LOOKUP_ENFORCE_ACL=1).

Switching back the setting to 0 and restarting the Traveler server solved the issue at customer site and the corporate lookups works again.

If you want to enforce the ACL you should check your ACL settings, so that the Traveler Server and your Traveler users are able to access the directories and most important the da.nsf on your mail and / or Traveler server.

1Oliver Regelmann  07/12/2013 9:59:05 AM  IBM Notes Traveler 8.5.3. UP2 IF2 may break Directory Lookup

Having this set to 1 might probably be what they actually want because otherwise their users could lookup names on their mobile device they're not allowed to lookup in Notes.

  • Hinweis zum Datenschutz und Datennutzung:
    Bitte lesen Sie unseren Hinweis zum Datenschutz bevor Sie hier einen Kommentar erstellen.
    Zur Erstellung eines Kommentar werden folgende Daten benötigt:
    - Name
    - Mailadresse
    Der Name kann auch ein Nickname/Pseudonym sein und wird hier auf diesem Blog zu Ihrem Kommentar angezeigt. Die Email-Adresse dient im Fall einer inhaltlichen Unklarheit Ihres Kommentars für persönliche Rückfragen durch mich, Detlev Pöttgen.
    Sowohl Ihr Name als auch Ihre Mailadresse werden nicht für andere Zwecke (Stichwort: Werbung) verwendet und auch nicht an Dritte übermittelt.
    Ihr Kommentar inkl. Ihrer übermittelten Kontaktdaten kann jederzeit auf Ihren Wunsch hin wieder gelöscht werden. Senden Sie in diesem Fall bitte eine Mail an blog(a)poettgen(punkt)eu

  • Note on data protection and data usage:
    Please read our Notes on Data Protection before posting a comment here.
    The following data is required to create a comment:
    - Name
    - Mail address
    The name can also be a nickname/pseudonym and will be displayed here on this blog with your comment. The email address will be used for personal questions by me, Detlev Pöttgen, in the event that the content of your comment is unclear.
    Neither your name nor your e-mail address will be used for any other purposes (like advertising) and will not be passed on to third parties.
    Your comment including your transmitted contact data can be deleted at any time on your request. In this case please send an email to blog(a)poettgen(dot)eu