top of page

Integration Designer 7.5 Could Cause Your User Account to be Locked Out

Are you suddenly experiencing frequent lockouts of your user account after you have recently changed your password? One important thing to note is that IBM Integration Designer does store the user ID and password that you initially set up to use with the servers that you created.  As you can see in the image below and by double clicking on the server that you have configured in your local test environment (or any other servers for that matter), IID stores the username and password for how it connects to Process Center and your servers.

What can happen here if you use your own user account is that IID will store the credentials your first provided when you set this server up.  When you change your password for your user account, this will update in your LDAP or Active Directory; however, IID will repeatedly try to connect using your old credentials, ignoring any authentication failures.  So, after the usual three incorrect attempts, or whatever your policy is, the user account will become locked out.  This will continue until you lock you out until you change the credentials here on the Security screen in IID for the configured servers you have in place.

Ideally, IID should not be retrying the connection after it receives an authentication failure and it should prompt you for you new password.  Yet, at this time, the product does not have that capability.  So, there are two options that IBM provides: 1) Use a service ID with a non-expiring password for these servers, or 2) Modify the field in this properties screen for the server status interval (default is 5000 msec). If you increase this number to a much larger number, the user will have time to come into IID and change their credentials before the account becomes locked out again.

In my opinion, the latter is not really a solution. Actually, neither appear to be a true solution to the problem, but nonetheless, in my experience, I would use another ID other than your own user account.

Share this:

  1. Facebook

  2. LinkedIn

  3. Twitter

  4. Email

0 views0 comments