Cloud Platform

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Not under consideration
Workspace WebSphere Liberty
Created by Guest
Created on Dec 2, 2021

Improve message detail for CWWKS1777E

Current format of message is as below:
ibm.ws.security.openidconnect.common.OidcCommonClientRequest E CWWKS1777E: Validation failed for the token requested by [RS_CREDENTIAL] due to a mismatch of signing algorithms between the OpenID Connect client and OpenID Connect provider. The signature algorithm for the client is [RS256] and the signature algorithm for the provider is [RS384].

This provides no useful information other than the mismatched algorithm. Request is to enhance message output to provide additional diagnostic data from the JWT headers available such as client_id, iss, sub at least.

In this case the call is a REST API call to z/OS Connect, so it would be even better if the requested API/service could be displayed.

This would help to match errors to clients and requests and speed up resolution.

Idea priority High
Why is it useful?

root cause analysis of errors displayed in server logs.

Who would benefit from this idea? everyone
  • Guest
    Jan 8, 2022

    Ok, I don���t see any text that says why the idea is now marked as not under consideration.

    Regards,

    Steve McAuliffe

    Mainframe transformation
    Technology Infrastructure
    Mainframe Enterprise Services
    Office: +44 207 996 6989