IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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.

Add a new idea Subscribe
Status Future consideration
Workspace z/OS
Categories JES2
Created by Guest
Created on Jul 30, 2018

RELATED IDEAS

UPDATE RACF APPCLU SESSKEY ENCRYPTION

o We are unable to connect JES2 NODES when SIGNON=SECURE is specified on systems secured by RACF and those secured by CA ACF2 and CA Top Secret. Nodes where RACF is in use on both NODES are connecting successfully albeit with a non-FIPS 140-2 compliant algorithm. RACF systems are apparently using ENCRYPT=(data addr,DES) on the RACROUTE call. The documentation states that when “,DES” is specified, the RACFDES algorithm (RACF's variation of DES) is actually utilized. The CA products use standard DES which is actually an option on the ENCRYPT= parm but cannot be specified on the RDEF/RALT APPCLU SESSION definition.
o This enhancement is requesting an update to RDEF/RALT APPCLU SESSION SESSKEY to allow for multiple encryption options including STDDES (for use right now with non-RACF systems) and a FIPS 140-2 compliant AES algorithm. Implementation of this feature can be modeled similar to the RALT/RDEF KERB ENCRYPT segment.

Idea priority Medium
  • Guest
    Reply
    |     Nov 1, 2018

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS
    Component - JES2
    Operating system - IBM z/OS
    Source - Client

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS
    Component - RACF
    Operating system - IBM z/OS
    Source - Client

  • Guest
    Reply
    |     Jul 30, 2018

    I would like to add some references to this RFE:

    Reference: Annex A: Approved Security Functions for FIPS PUB 140-2, Security Requirements for Cryptographic Modules
    Reference: CA Support Issue 01142078

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.