How to restrict some users access to HCL Connections by Domino LDAP group, not by OU?

Hello, I have the HCL Connections 6.5 CR1 in the Linux - RHEL 7.8 environment. Domino LDAP is used for user authentication.

We have a total of 1000 users in Domino LDAP, and we want to allow only 400 user access to Connections login through the Domino LDAP group? Kindly share the steps to achieve it.

Thank you in advance.

Regards,

Elango

Hi Elango Gopal ,

Their will be two scenarios

1. If user are not sync with PEOPLEDB or if you user are not populated .

Then i will suggest dont populate those user , customize collect.dns with the required user and

run populate_from_dn_file.sh to populate only desired user which need to login

2. if users are already populated to people DB or synced

You can mark those user as inactive , below is the technote which might be usefull

https://help.hcl-software.com/connections/v6/admin/admin/t_admin_profiles_delete_users.html#:~:text=Use%20the%20delete_or_inactivate_employees%20command%20to,Connections%20applications%20is%20not%20removed.

Regards

This approach will not hide other users from WebSphere and they will be able to login to Connections if the wish to. After logging in they will of cause observe a various set of error messages as Connections will not serve users missing from profiles. But if speaking strictly about login they will be able to do it.

Hi @Shrishti Raj Singh Thanks for your response.

As @Anatoly Kireev said, WebSphere will automatically allow the user authentication to Connections even though we have restricted users in peopledb through TDI.

Yes, we will get an error of access denied when we didn't populate the user profile or applied restriction through TDI.

Is there feasibility to apply the user access restriction to Connections login based on Domino group. Thanks.

I guess the easiest way is to put those 400 users to a separate OU in Domino LDAP and then use this unit's DB as a BaseDN making all other parts of your LDAP invisible to WebSphere and Connections.

Thanks, @Anatoly Kireev for the response.

Yes, we can achieve it by LDAP OU, but the Customer requested us to restrict users by Domino group instead of OU.

The customer asked me to restrict based on the Domino group because how can restrict 5 users and allow 5 users in existing HR_OU which is OU already belonged to Domino webmail OU.

Hello Elango,

Your requirement is possible with ldap user filter configuration. You add user filter that should matches to objectclass and specific group name.

Add this filter in user registry configuration in WAS console , profile_tdi.properties file as well.

Thanks,

Venkat

@Venkatanaraya Konal Thank you for your response. I think the filter can be applied for OU or Organization only. Would you please share the group based sample filter parameter for WAS or TDI.

Thanks in advance.

Hi Elango,

Search filter to verify users who are part of specific group works in AD ldap. But as Martin said, it seems it will not work for Domino. I would suggest you to follow steps provided by Martin.

Thanks,

Venkat

Hi Elango,

unfortunately you need to tell your customer that this is not possible with Domino LDAP.

To achieve this, a filter like this must be supported by the LDAP:

"(&(mail=martin.schmidt*)(dominoaccessgroups=CN=CNXUser))"

Active Directory supports this type of filter, Domino not. (This was discussed in the last 10 years but IBM never implemented it.)

So the only solution you have is to add an attribute (e.g. CNXAccess) to every person document (maybe a scheduled agent that manages this attribute based on groups). No Schema extension necessary.

The result would be a filter like:

"(&(mail=martin.schmidt*)(CNXAccess=1))"

When you have this attribute, you can use it in the TDI LDAP Filter and in WebSphere -> Security -> Federated Repository -> your LDAP > Federated repositories entity types to LDAP object classes mapping -> Person Account -> Search Filter -> (CNXAccess=1)

Martin

Hello Martin, Thanks for your response. Do you have an idea why the Domino LDAP is supported for the group, its limitation, or the group feature unavailable in Domino? Kindly do clarify. Thanks.

Hi Elango,

as I'm not from HCL nor IBM, I can't give you a definitive answer. I is based on my experience and some guessing.

Withing the Domino Name and Address Book, there is no link from a person document to any groups the user is member of. The groups just contain the list of names of the users which are part of this group.

In Domino there is no API to get a collection of person documents for all members of a group. You always get the group document, then the list of member names and then search for all person documents based on the member list from the group using a loop.

The same is true for LDAP. You can get the members of a group and then search each member.

The "DominoAccessGroup" attribute in LDAP is only a virtual attribute, calculated on the fly, when the person document is already looked up. So the lookup is : Get all groups, the user is member of.

So in summary:

Due to the organization of data in the name and address book, there is no feature in domino to get all person documents based on the group name only and therefore this function can not get exposed via LDAP.

You always can work around doing multiple queries (this is what WebSphere does in the group settings). But for your question, there is no implementation doing it with only 1 query / filter.

Hope this helps.

Martin

Thanks, @Martin Schmidt for the response in detail.