Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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

Post 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 product management 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 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Planned for future release
Created by Guest
Created on May 6, 2021

zCEE and DVM using JWT token for authentication

Wile executing a RESTful API that uses a Data Virtualization Manager service, it is resulting with an AVZ7200E abend when a JWT token is used for authentication/authorization. The same API is executed properly with no abend when using Basic Authentication.

The JWT token includes a distributed userid, which has been mapped to a valid RACF userid, When executing the API, zCEE sees the mapped RACF userid and uses this RACF userid for authentication; if properly authenticated, control is passed to DVM with both the distributed userid and valid RACF userid. The Service provider, in this case, DVM, is expected to use the RACF userid as the trusted credential that will access the backend data.

However, the trace shows that DVM is using the distributed userid instead of the valid RACF userid, i.e. GET "userid" https://server host name:port number/dvs?refresh resulting with the AVZ2700E error (9903010 with Uid vector bad length since the distributed userid usually does not follow the 8-character length of a userid. This will only work if we use a distributed userid in the token that is a;lso a valid RACF userid; but distributed Active Directory userids are not limited to the mainframe standard 8-character length for a userid.

With CICS service provider, this error does not occur; CICS uses the mapped RACF userid accordingly when a JWT token is used for authentication.

DVM can work the same way if it can be changed to use the mapped RACF userid as well, instead of the distributed userid. Because of this error, we are unable to implement in production the DVM APIs using a JWT token for authentication. Developers are reverting the use of DVM for this reason.

Needed by Date May 31, 2021
  • Guest
    Mar 15, 2022

    Please provide a target date when this will be resolved and available for us to use; without the ability to use JWT token for DVM APIs, we are unable to leverage DVM. Thank you.

  • Guest
    Jun 29, 2021

    The AHA DVMZ-I-71 is being reviewed by Dev to determine if it will be incorporated into DVM or not.

  • Admin
    Doug Dailey
    May 7, 2021

    Thank your for the enhancement request. We will be reviewing your request and others next week.