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.