Skip to Main Content
Cloud Platform

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

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 a notification 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.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Future consideration
Workspace WebSphere Liberty
Created by Guest
Created on Nov 11, 2021

imcl not usable if usrprf has password *none

We started using ansible for managing our ibm i platform.

We host a large websphere environment on it.

I started to do the updates of Express and liberty via ansible.

The first approaches did not work because of imcl complaining about the ansible user which was not a root or Administrator for imcl, altough it had all rights auf a secofr user.

The issue was also recreateable within qsh on the local host.

I opened a case at ibm and got the cause:

For using ansible i created a seperate secofr user. For security reasons i set the password to *NONE, because the access from ansible is done only via ssh-keys.

That works for most of the things we do, but not for using imcl.

Imcl uses jt400 in the background. and that does not work with a user having a password set to *none.


So the workaround i do is, when using imcl, i set a password before to a dummy string, do the imcl things and afterwards set the password back to *none.


But i guess for security reasons, this should be fixed.

Idea priority Medium