Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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.


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
Workspace IBM i
Created by Guest
Created on Apr 28, 2020

Provide API to disable Netserver user

With an ever increasing risk of getting infected by mal and ransomware it is important to have more control over Netserver.

In an exit program we try to detect such instances but would like to take appropriate actions like disabling the users Netserver access (disabling the OS account itself has no impact) which is currently not possible.

It would be handy to extend the QZLSCHSI API with the option to not only enable a Netserver account, but also disable a Netserver account.


Use Case:

In an exit program we try to detect suspicious file actions but would like to take appropriate actions like disabling the users Netserver access (disabling the OS account itself has no impact) which is currently not possible.


Idea priority High
  • Guest
    Reply
    |
    Jun 8, 2020

    While the "logical" access is an important feature in securing the IFS, it still doesn't guarantee that people get infected by ransomware which could also impact the IFS. For this reason we wrote an exit program that detects suspicious behavior and disables the user (which is currently solved by disabling the OS/400 account, however the Netserver account should be sufficient).

  • Guest
    Reply
    |
    May 15, 2020

    Thank you for submitting this request. We agree that the ability to secure connections to IBM i NetServer is extremely important. However, we feel providing an interface to disable the NetServer user is not the best way to do this. Instead we feel the request listed in RFE 107575 is a much better way to secure connections and restrict users. We feel that there should also be a 'logical authority' set for the server itself to allow restricting user access to IBM i NetServer.