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 Delivered
Workspace IBM i
Categories Security
Created by Guest
Created on Nov 27, 2017

Configure telnet with SSL/TLS via command

Provide API/command to supply telnet with a self-signed digital certificate (most likely created with openssl).


Use Case:

Today there are many manual steps(n1) required to secure telnet. The steps to secure telnet could be made as simple as running a couple commands; similar to how simple it is to generate self-signed certs with openssl for web apps(n2).

n1: https://support.litmis.com/single-tenant/tlsssl-telnet.html

n2: https://krengel.tech/kt-securing-nodejs-server-self-signed


Idea priority High
  • Guest
    Reply
    |
    May 6, 2022
    This Idea/RFC was has inadvertently left in the incorrect external state. IBM believes that the request described was solved and has been available for several years.

    For more information, see Digital Certificate Manager APIs: https://www.ibm.com/support/pages/node/1120281

    IBM Power Systems Development
  • Guest
    Reply
    |
    Oct 8, 2020

    The ability to automate certificate management for a secure Telnet connection is available via APIs.
    1. Import the PKCS#12 file from OpenSSL into the *SYSTEM certificates store: QykmImportKeyStore.
    2. Remove the old certificate from the Telnet server application using API: QycdRemoveCertUsage.
    3. Add the new certificate to the Telnet server application using API: QycdUpdateCertUsage.
    4. If you also need to add a CA certificate to the CA trust list, use API: QycdAddCACertTrust.

  • Guest
    Reply
    |
    Apr 16, 2018

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Security
    Operating system - IBM i
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Networking
    Operating system - IBM i
    Source - None

  • Guest
    Reply
    |
    Apr 16, 2018

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Networking
    Operating system - IBM i
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Security
    Operating system - IBM i
    Source - None

  • Guest
    Reply
    |
    Feb 13, 2018

    IBM i Limited Availability APIs already exist to complete the same steps which are defined in example "n1" including creating a Local CA, creating a server certificate issued by the Local CA, assign the server certificate to an application ID, and define the CA in a trust list.

    We have plans to convert most of these limited availability APIs to general availability APIs in a future release which can be used by anyone who wants to write their own command for automating these tasks.

  • Guest
    Reply
    |
    Feb 13, 2018

    The CAAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed. Making it easier to secure a system is a good thing -- not needing to go into DCM would be better.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.

    For more information about CAAC, see www.common.org/caac

    For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/

    Nancy Uthke-Schmucki - CAAC Program Manager