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 BCP_SMF
Created by Guest
Created on Oct 22, 2024

RELATED IDEAS

Signed SMF Records - Validation must be possible with any Token name (holding the pubic key)

We are using SMF dual signature (RECSIGN and ARECSIGN) which works as expected. However, we have a problem with the validation of the records.
We have a specific naming pattern assigned to our Tokens (as referenced in SMFPRMxx) member. All our systems (split into three Sysplexes) are writing signed records but as they have different data retention periods and availability SLAs we are transferring all our data to the production systems to keep the records for a long time. As stated in the documentation (https://www.ibm.com/docs/en/zos/3.1.0?topic=records-using-ifasmfdp-validate) at step 2. only the public key is required for the validation. Hence we exported all the public keys from the source systems into our production systems to perform the the validation. However, that is not possible as the Token name has a different naming but SMF requires the token name to equal (which is not a cryptographic requirement - only the public key is required for this validation).
Due to that fact, we cannot validate the records with a different Token name.

Essentially, my idea is for SMF to support the use of the public key under multiple different token names. This will allow different systems with different naming standards the ability to validate SMF data using a different name.

Idea priority High

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.