Skip to Main Content
Digital Business Automation Ideas


This is an IBM Automation portal for Digital Business Automation products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):
  • Cloud Pak for Business Automation - including Business Automation Studio and App Designer, Business Automation Insights

  • Business Automation Workflow (BAW) - including BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management

  • Content Services - FileNet Content Manager

  • Content Services - Content Manager OnDemand

  • Content Services - Daeja Virtual Viewer

  • Content Services - Navigator

  • Content Services - Content Collector for Email, Sharepoint, Files

  • Content Services - Content Collector for SAP

  • Content Services - Enterprise Records

  • Content Services - Content Manager (CM8)

  • Datacap

  • Automation Document Processing

  • Automation Decision Services (ADS)

  • Operational Decision Manager

  • Robotic Process Automation

  • Robotic Process Automation with Automation Anywhere

  • Blueworks Live

  • Business Automation Manager Open Edition

  • IBM Process Mining


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Not under consideration
Created by Guest
Created on May 28, 2024

Create additional parameters in ars.cfg to be used specific for ARSLSYNC to separate them from normal LDAP config instead of being shared parameters for both LDAP & ARSLSYNC

Create additional parameters in ars.cfg to be used specific for ARSLSYNC to separate them from normal LDAP config instead of being shared parameters for both LDAP & ARSLSYNC

Summary
Currently the LDAP Parameters configured in ars.cfg locally on the CMOD Library Server (LS), points to our LDAP Proxy, which federates between multiple LDAP servers.

This is problematic when running ARSLSYNC, as we would like to point to a specific LDAP server with specific parameters also set for BASE, BIND, MAPPED & ALLOW_ANONYMOUS.

It would be great if we can have a separate section in ars.cfg specific for above ARSLSYNC config. This will then allow us to share the same ars.cfg file with required parameters for both LDAP Proxy & ARSLSYNC on the local CMOD Library Server (LS).

Details of Requirement

For us, it is important to specify the below 6x parameters for our LDAP Proxy, separate from the parameters used when running ARSLSYNC:

ARS_LDAP_SERVER=

ARS_LDAP_PORT=

ARS_LDAP_BASE_DN=

ARS_LDAP_BIND_ATTRIBUTE=

ARS_LDAP_MAPPED_ATTRIBUTE=

ARS_LDAP_ALLOW_ANONYMOUS=

On the positive side, IBM L2 have already indicated that the below two parameters are available to be configured specific for ARSLSYNC, which is very good news!

ARS_LDAP_SYNC_SERVER

ARS_LDAP_SYNC_PORT

To address our requirement to accommodate both LDAP Proxy & ARSLSYNC on the local CMOD Library Server (LS), we are asking for the possibility of also creating additional parameters for below 4x parameters to be used specific for ARSLSYNC, to separate them from the normal LDAP config in ars.cfg:

ARS_LDAP_BASE_DN=

ARS_LDAP_BIND_ATTRIBUTE=

ARS_LDAP_MAPPED_ATTRIBUTE=

ARS_LDAP_ALLOW_ANONYMOUS=

This will then allow us to share the same ars.cfg file with required parameters for both LDAP Proxy & ARSLSYNC on the local CMOD Library Server (LS).

Idea priority Urgent
  • Admin
    NEIL Parrott
    Reply
    |
    Aug 13, 2024

    ARSLSYNC was designed specifically to run on the same machine as the CMOD Server.

    Our product architect has confirmed that ARSLSYNC does not actually talk to LDAP, it only talks to ARSSOCKD (which in turn talks to the LDAP server).

    Advised of the configuration parameters below which can be set in ars.cfg specific for ARSLSYNC to be able to point to a different LDAP server and set the LDAP Paramaters required for ARSLSYNC.

    • ARS_LDAP_SYNC_SERVER

    • ARS_LDAP_SYNC_PORT

    There are no plans currently to change how this works.

  • Admin
    NEIL Parrott
    Reply
    |
    Jun 4, 2024

    I see from case https://w3.ibm.com/tools/caseviewer/case/TS016230122 that you will follow up with your Sanlam teamand provide additional feedback .


    Just to reiterate. The proxy will ultimately point to the same LDAP Servers, meaning the base and bind attrs will be the same. Further, most LDAP servers don’t support anonymous bind, so that parm is irrelevant. Mapped attribute is also irrelevant because It’s used only for authentication.

    Think of it this way. If we sync users with one configuration, we also then need to authenticate them. To ensure that that the authenticated user matches the synced user, the configuration needs to be the same.