LI81640: NEW API DEFINITION IS FAILING WHEN TRYING TO HAVE OAUTH SECURITYDEFINITION ALONE

APAR status

• Closed as program error.

Error description

• Creating an API with OAuth security definition and deleting the
  Client ID security definition which is created by default may
  result in validation errors because a name property is added.
  For example
  Validation errors:
  line 0:
  Additional property name is not allowed
  line 19:
  Must validated one and only one schema (oneOf)
  Sample security definition:
  securityDefinitions:
    newDef:
      type: oauth2
      flow: accessCode
      x-ibm-oauth-provider: testoauth
      authorizationUrl:
  'https://$(catalog.url)/testoauth/oauth2/author ize'
      tokenUrl: 'https://$(catalog.url)/testoauth/oauth2/token'
      scopes:
        sample_scope_1: Sample scope description 1
      name: newdef
  

Local fix

• Remove the name property to resolve the validation errors
  

Problem summary

• When saving API Security definitions, the UI is adding the
  "name" property for all security definitions when it should only
  be for 'apiKey' type definitions.
  

Problem conclusion

• <span style="background-color:rgb(255, 255, 255)">The fix is
  targeted for inclusion in IBM API Connect 2018.4.1.13.</span>
  

Temporary fix

Comments

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

  API CONNECT ENT

• Fixed component ID

  5725Z2201

Applicable component levels