6.5 iNotes chat with SameTime using LDAP?

Is anyone else using this configuration? I can’t seem to get any awareness or chat functionality working within my iNotes clients.

My SameTime server is working just fine for both the ST Connect client and the ST applet.

I have followed the documentation in the admin help and also in the IBM redbook. The only difference in my configuration is that we’re using LDAP and not just straight Domino directories.

There seems to be a lot of neglect in the documentation for people using LDAP. The awareness in the 6.5 client doesn’t exactly work when you’re using LDAP either. I had to make a bunch of changes to the mail template just to make things work.

Any help or related information would be greatly appreciated.

Thanks,

Tony Shuba

BlueStorm Technologies Inc.

Subject: The easiest way to integrate is to modify the LDAP Schema…

We added the field AbbreviatedName to the $PersonExtensibleSchema subform with the formula of @Name([Abbreviate]; FullName). Then modify the LDAP Schema Databaseand add

Names

Syntax

LDAP name:

AbbreviatedName

Syntax type:

1.3.6.1.4.1.1466.115.121.1.15

Alternative names:

OID:

id-at-DominoAbbreviatedName

Notes mapping:

AbbreviatedName

Schema:

Domino

Then in your Configuration document add AbbreviatedName to your attributes.

LDAP Attribute Types:

AbbreviatedName
AltFullname
dominoCertificate
FullName
givenName
HTTP-HostName
ListName
Location
mail
MailAddress
MailDomain
MailFile
MailServer
member
sn
uid

Domino Fields:

AbbreviatedName
AltFullname
Certificate
FullName
FirstName
HTTP_HostName
ListName
Location
InternetAddress
MailAddress
MailDomain
MailFile
MailServer
Members
LastName
ShortName

Then finally on your Sametime Server in the Sametime configuration database, LDAP Configuration

Search filter for resolving person names:(&(objectclass=organizationalPerson)(|(cn=%s*)(givenname=%s*)(sn=%s*)(mail=%s*)(abbreviatedname=%s*)))

Search filter to use when resolving a user name to a distinguished name: (&(objectclass=organizationalPerson)(|(cn=%s)(givenname=%s)(sn=%s)(mail=%s)(abbreviatedname=%s)))

Subject: RE: The easiest way to integrate is to modify the LDAP Schema…

Thank you for the information Bill.

I will definitely give this a try and post my results.

As you’ve outlined, we have also determined that the basic problem with the SameTime integration is that the “abbreviated” name is not typically available through the basic LDAP schema.

I’ve taken a less elegant approach by modifying some basic code in the mail template, replacing the Abbreviate with CN parameters in the @Name formulas.

I certainly see how this will solve the issues within the full Notes client.

Has this also resolved the issue for you when using the iNotes interface thru the browser?

Thanks.

Tony

Subject: Results and Some Success

I have followed the suggestions here and it does solve the problem using the Notes client.

I had a few issues with adding the new attribute to the LDAP Schema database. Trying to use your exact values for OID kept giving me an error when I attempted to save the document.

Finally, I was able to add the new attribute then add it to the list in Configuration document. I was able to do an LDAPSearch and verify the value as well.

I modifed the search filter on the SameTime server and it began to work perfectly. So I’ve been able to revert all my user’ mail files back to the standard iNotes6.ntf, which is really where I want them to be.

However and unfortunately, this has not seemed to help iNotes (DWA) interface at all. I still can not see any awareness or even the “chat” link that is supposed to show up.

Does anybody know the trick to this one?

Thanks,

Tony

Subject: RE: Results and Some Success

I had domino web access and chat working fine in my 6.0.3 environment, as soon as I moved my enterprise server to 6.5.1, the chat funtion within iNotes is gone. My sametime server is still on 6.0.3. I have yet to do in depth testing on this, but I bet the two versions are not compatible. I will post this as a main topic and see what I get in response.