IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Updating Password automatically in the FileAgent

Hello,


We are using CD version : IBM_CD_V4.3_UNIX_Linux_Red_Hat.

 

We need to install CD and FileAgent for our multiple internal BU servers.

As you know - we need to use username and password for FileAgent. Please note that we are using common ldap/domain userid and password for these FileAgents. However, we got password expiration policy set for this ldap userid. So every 90 days this ldap user password would be expired.
The problem is here .. whenever we are changing this ldap/domain password, we will have to login manually to our lots of BU servers; and need to update the new password on each File Agent manually. It is becoming very tough to update password in all of our internal BU servers who got FileAgent installed.

Hence, we need a way to update new password automatically in the FileAgents of all of our internal BU servers.

  • Guest
  • Jan 24 2020
  • Future consideration
Connect:Direct / Administration & Configuration
What is your industry? Financial Markets
How will this idea be used?

We are using CD version : IBM_CD_V4.3_UNIX_Linux_Red_Hat.

 

We need to install CD and FileAgent for our multiple internal BU servers.

As you know - we need to use username and password for FileAgent. Please note that we are using common ldap/domain userid and password for these FileAgents. However, we got password expiration policy set for this ldap userid. So every 90 days this ldap user password would be expired.
The problem is here .. whenever we are changing this ldap/domain password, we will have to login manually to our lots of BU servers; and need to update the new password on each File Agent manually. It is becoming very tough to update password in all of our internal BU servers who got FileAgent installed.

Hence, we need a way to update new password automatically in the FileAgents of all of our internal BU servers.

×

Attachments Open full size

  • Guest commented
    20 Jan, 2021 11:48am

    The latest File Agent also supports specifying your credentials in an external Java Connection Utility (JCU) file. The JCU file can be managed separately from the File Agent configuration file itself. It allows you to easily update your credentials from the command line. No need to use the GUI.

    If you are using common credentials and IP/port across all your File Agents, then may even copy the same JCU file to them.

    See File Agent fix list: 

    1.4.0.0_iFix033) MFT-9055  date: 2018/09/13
    -------------------------------------------
      Add support for connecting to a Connect:Direct server using a Java
      Connection Utility (JCU) file. A JCU file contains all required connection
      information, including the server's address and user credentials.
      To enable the use of a JCU file:
      (1) Type the value jcu in both the Userid for API and the Password for
          API fields.
      (2) Create or update the JCU file by running the following command line from
          the File Agent directory:
          java -classpath CDJAI.jar com.sterlingcommerce.cd.sdk.JCU "-fcddef.jcu" 
          Enter Node, Address, Port, UserId, Password and Protocol ("tcpip") for
          your CD node.
          Note that the associated fields from the File Agent configuration will
          be ignore for this connection.
    ×

    Attachments Open full size

  • Admin
    Chris Sanders commented
    28 Feb, 2020 04:22pm

    Thank you for opening this enhancement request with IBM. I have reviewed it with my team and believe this would be a valuable enhancement to Connect:Direct. We will look to expand certificate based authentication to File Agent. Cert auth is currently available for Control Center and REST API connections to C:D and is our strategic target to minimize password maintenance for automated authentication needs. I will accept this request as an uncommitted candidate and we will look to add it to the C:D roadmap moving forward.

    Sincerely,

    Chris Sanders

    Connect:Direct Offering Manager

    ×

    Attachments Open full size

  • Guest commented
    21 Feb, 2020 03:05pm

    The latest releases of Connect: Direct and FileAgent, allow you to leave the password field empty, as long as it is properly configured in User Authorities. Have you tested it?

    Note FileAgent:
    fix 00000043 2019/05/24 CDWA-748 Updated IBM Application Interface for Java (AIJ) to allow an empty API password

    ×

    Attachments Open full size

Related ideas

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.