PH25185: The Authorization header is not present in the swagger.json when there is a slash before the query parameters.

APAR status

• Closed as unreproducible in next release.

Error description

• When there is a slash before the query parameters (e.g.
  /operationPath/?myQueryParameter) the expected Authorization
  header is missing from the swagger.json generated by the z/OS
  Connect EE API toolkit.
  
  The Authorization header is present in the request.map.
  

Local fix

• Remove the slash immediately before the query parameter
  e.g. /operationPath/?myQueryParameter
  becomes
  /operationPath?myQueryParameter
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of z/OS Connect EE V3.0            *
  ****************************************************************
  * PROBLEM DESCRIPTION: The Authorization header is not present *
  *                      in the swagger.json when there is a     *
  *                      slash before the query parameters.      *
  ****************************************************************
  z/OS Connect EE API toolkit does not generate swagger for a path
  that ends in a forward slash ("/") before a query parameter.
  
  For example the following path: "/newpath/?queryparm", does not
  (re)generate the expected swagger.json file.
  

Problem conclusion

Temporary fix

Comments

• The z/OS Connect EE API toolkit has been updated to generate the
  appropriate swagger.json file in the case where the path ends
  with a forward slash before the query parameter.
  
  This fix is expected to be delivered with z/OS Connect EE API
  toolkit v3.0.84 and v3.2.84
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  Z/OS CONNECT EE

• Fixed component ID

  5655CE300

Applicable component levels