The Connections Blog

Number one:

LO48384: WHEN USER HAS UID = MAIL ADDRESS, POPULATE_FROM_DN SCRIPT WILL CREATE DUPLICATE ENTRIES IN PROFILES DB.

Problem summary

When the 'uid' column is mapped to a value other than 'uid' then TDI will create duplicate entries in Profiles database.

Problem conclusion

Summary
In the SyncDBFromSource assembly line, the assembly line is hard-coded to use the work['uid'] attribute rather than the db_from_ldap mapping of the value.  As a result, it tries to match the user based on the LDAP[uid] attribute, irregardless of the configuration.

Prerequisities
None

Install Instruction:
1. Backup the profiles_tdi.xml file in TDI 2.5 solution first
2. Unzip LO48384.zip to TDI 2.5 solution directory, and replace the changed file as below:
/profiles_tdi.xml

Ouch!  Get this one on ASAP if you're not using 'uid' as your standard Connections ID.

And number two:

LO46073 Profiles: ATOM API breaks when 'reader' role is mapped to all auth

Abstract
ATOM API breaks when "reader" role is mapped to all authenticated.

Problem Description

To reproduce:

1. Map the reader role to all authenticated.
2. Attempt to access a 'read-only' Profiles ATOM API not using preemptive authentication such as the profile service document.

Expected result: prompted with basic authentication.
Actual result: prompted with forms authentication.

Conclusion
Towards the end of 2.5, an unnecessary security constraint was added to the web.xml that applies FORMs auth rules to the Profiles ATOM API. As a result, when the application is locked down, rather than returning a BASIC auth prompt, the application redirects the API callers to a forms login page.

Whilst pre-dating FixPack1 (2.5.0.1) this fix seems to need reapplying after the fixpack is installed.  This is particularly important if you are looking to run the new RIM client for Lotus Connections or any other application that relies on the ATOM feeds to access Profiles content.

By: Stuart McIntyre - Connections | 0 Comments | On: 1 March 2010 06:19:22 | Tags:  connections  lotus  fix 

Comments

No Comments Found