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 (

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 Delivered
Workspace IBM i
Created by Guest
Created on Dec 18, 2019

Allow Kerberos to be specified as primary authentication for QNTC

Users that have SSO/Kerberos/EIM are forced to choose between being enabled for file transfers to the QNTC (windows network) or having local password management. Users should be able to use the system locally and still have file transfer authentication via Kerberos.
QNTC was not created for general use but was narrowly defined for the old FSIOP integrated server. QNTC has worked for many of us but it is not being maintained in consideration of more modern authentication. It uses the local password management attribute of the user profile to determine how to authenticate. If local password management is *no then it will use Kerberos network authentication but this setting prevents local uses of the IBM account. I have 3 examples of this causing problems for us below. If local password management is *yes then QNTC attempts to authenticate using encrypted passwords but then the account name on the windows domain and the IBM must be the same. This is not possible when the corporate standard for windows user names is to use long friendly names like Providing a means of switching a system value to cause Kerberos to be used preferentially for QNTC would resolve the issues we are having

Use Case:

I have a planner who needs to be able to sign herself on to 5250 emulation somewhere deep in the factory to fix a problem but then because she has local password management *yes to enable that then she cannot upload or download files using QNTC scripted *cl programs in her office to import planning schedules and EDI files from customers. Or I have a AP clerk who needs to be able to sign in to a check writing program to print MICR checks on a laser printer from i data. And just like the planner above because she has local password management *yes she cannot use scripted QNTC in a cl program to upload cash application data, that she gets from the bank, to the i . Or I have a supply chain manager who wants to use her password to sign into a screen scraped GUI version of what we normally see on 5250 emulation and this GUI program is not compatible with SSO so now because she has local password management she cannot download the production schedule to excel anymore. In these cases QNTC is using encrypted password authentication despite the fact that network authentication via Kerberos is available. Note that QNTC has been in use for a long time but with new corporate naming standards forcing us into using EIM and Kerberos, QNTC needs to be updated to keep up with modern authentication.

Idea priority Medium
  • Guest
    May 3, 2022
    This is available in IBM i 7.5.
    The QNTC file system has changed the configuration requirements for Kerberos. The user profile local password management option (LCLPWDMGT) is no longer required to be set to *NO. QNTC will now attempt to use Kerberos enablement first but may fall back to use the password.

    See the IBM i Documentation on QNTC for more information.
  • Guest
    Jan 13, 2020

    Thank you for submitting this request.

    We agree that the QNTC design to support Kerberos/EIM is restrictive. The development team will investigate options and consider this in our plans.