Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform 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 (

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.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your 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