× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Nathan,

Saying the doco is hard to follow is very generous, it's some of the worst
documentation I have ever seen.

Try changing your bind name to cn=ldapquery.

So instead of this:
Bind name: cn=ldapsearch,o=ourcompany,c=au

Use this:
Bind name: cn=ldapquery,o=ourcompany,c=au

Hope this helps!
Kim
----------------------------------------------------------------------------------------------

Kim Greene
Kim Greene Consulting, Inc.
President
Domino consulting, education, and performance
Office: 507-216-5632 Mobile: 507-254-9353
Email: kim@xxxxxxxxxxxxx Web: www.kimgreene.com
Blog: DominoDiva LinkedIn: kimgreeneconsulting Twitter:
iSeriesDomino



From: Nathan Simpson <nathan@xxxxxxxxxx>
To: domino400@xxxxxxxxxxxx,
Date: 09/16/2013 08:16 PM
Subject: Re: Upgrading to SSC and LDAP settings
Sent by: domino400-bounces@xxxxxxxxxxxx



This is what the LDAP Settings look like


LDAP Configuration Summary
Click Finish to save this configuration or Cancel to abandon and run the
guided activity again.

LDAP Configuration Settings:


Host name: ldap.ourcompany.com.au

Port: 389

Is anonymous? No

Bind name: cn=ldapsearch,o=ourcompany,c=au

Is secure LDAP connection? No

LDAP base entry: O=OURCOMPANY,C=AU

LDAP Type: Domino LDAP

User object class: inetOrgPerson

LDAP user search base: O=OURCOMPANY,C=AU

Policy ID for users and groups: dominounid

Display name: cn

Email address: mail

Similar name distinguisher: uid

Membership attribute:

Home Sametime server:

Authentication attributes: mail;cn;uid

Search attributes: mail;cn;uid

Group object class: groupOfNames

LDAP group search base: O=OURCOMPANY,C=AU

Display name: cn

Similar name distinguisher: cn

Member attribute: member




From: Nathan Simpson/AWH/AU
To: domino400@xxxxxxxxxxxx
Date: 17/09/2013 10:42 AM
Subject: Upgrading to SSC and LDAP settings


Hi,

We have been using Sametime, now running 8.5.2 IFR1 on Domino 8.5.3, for
quite some time and now want to move to SSC and Proxy etc so we can use ST

on iPads and the web.

We really only use the IM part of ST but who knows what the future holds.

Anyway, after a fair bit of messing around getting ST to work using an
LDAP directory we now need to sort out SSC and register ST to SSC.

I am not an LDAP expert so am having a bit of trouble knowing what
settings to use when registering the LDAP server in SSC.

The LDAP server is a Domino server (9.0.0). All of these servers run on
the same IBM i .

I think I am registering the LDAP in SSC wrong because I can't register
the ST server with SSC using registerSTServerNode.sh as it comes back with

AIDSC0919E: Login failed. Please verify the Login attributes

What are the settings to use for registering the LDAP with SSC? Do I need
to use the Advanced Settings? And do I just use the Domino administrator
ID to register ST to SSC.

A lot of questions but I found this doco hard to follow.

Thanks
Nathan


_______________________________________________
This is the Lotus Domino on the IBM i (AS/400 and iSeries) (Domino400)
mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.