Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 (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
Created by Guest
Created on Dec 6, 2017

MFA passticket support adjustment

Currently, MFA passticket support requires the use of the AZFPTKT1 factor and 2 associated TAGS to be specified on the RACF USERID:
ALU LOGIN ID MFA(FACTOR(AZFPTKT1)
ACTIVE TAGS(WINDOW:numseconds MFAFIRST:Y|N))

The MFAFIRST TAG specifies whether to require a successful IBM MFA logon prior to
the PassTicket being evaluated.
The WINDOW TAG sets the evaluation window, as a number of seconds. Said another way, the WINDOW is the amount of time that's passed since the user was last authenticated via MFA on the specific LPAR where the authentication request is being made.

This value should be sysplex-wide, not LPAR-specific, so that if a user successfully logged on to another LPAR in the sysplex, that elapsed time is taken into consideration.

Idea priority High