LI82648: ERRORS MIGRATING OIDC APIS FROM V5 TO V10

APAR status

• Closed as program error.

Error description

• When pushing a singular catalog from our provider org, we are
  noticing some errors when trying to migrate our OIDC APIs. For
  example, we received a warning on a few of our APIs when we did
  the AMU "unpack" command (see "ODIC unpack error.txt"). the
  referenced lines in the api from that warning. And we also
  received an error of not being able to create OAuth Provider /
  unknown OAuth provider when performing the AMU "push" to v10 of
  the catalog. We are using the v5-compatible gateways.
  
  
  ERRO[2022-06-02T14:00:13-04:00] AMUAP014E: The Oauth provider
  oauth-f3be1b521e5aff24f603a6dfecxxxxx could not be created in
  the target system.
  Reason: 400:
  [Error validating the request body against definition
  '#/components/schemas/OauthProvider']
  [(Request)/third_party_config/authorize_endpoint must match
  format "uri" (key: line: 14, column: 8) (value: line: 14,
  column: 30)]
  Location: cloud/provider-orgs/abcd/oauth-providers/oauth-f3be1b
  521e5aff24f603a6dfecxxxxx.yml
  ERRO[2022-06-02T14:00:53-04:00] AMUAP014E: The Configured oauth
  provider oauth-f3be1b521e5aff24f603a6dfecxxxxx could not be
  created in the target system.
  Reason: 400:
  [The 'oauth_provider_url' property value '/api/orgs/abcd/oauth-
  providers/oauth-f3be1b521e5aff24f603a6dfecxxxxx'does not refer t
  []
  Location: cloud/provider-orgs/abcd/catalogs/development2/spaces
  /mis/configured-oauth-providers/oauth-f3be1b521e5aff24f603a6dfe
  cxxxxx.yml
  ??Oneoferror from validation of API '??https://ecurep.mainz.de.
  ibm.com/ae5/#id=TS009578891&path=TS009578891%2F0-all_data%2F&fi
  lepath=TS009578891%2F0-all_data%2FOIDC_unpack_error.txt
  ARN[2022-05-26T11:35:13-04:00] AMUAU005W: product
  pet-mobile-apis-product:1.0.0 requires updating before it can be
  pushed to a target system.
  Reason: Product pet-mobile-apis-product:1.0.0 includes content
  with validation errors:
  Error validating API cloud/provider-orgs/abcd/catalogs/developm
  ent2/spaces/pet/products/pet-mobile-azure-odic-api-1.0.0.api.yml
  
  - Must validate one and only one schema (oneOf) (context:
  (root).securityDefinitions, line: 2128, col: 3)
  
  - securityDefinitions.authorizationUrl Does not match format
  'uri' (context: (root).securityDefinitions.authorizationUrl,
  line: 0, col: 0)
  
  - securityDefinitions.tokenUrl Does not match format 'uri'
  (context: (root).securityDefinitions.tokenUrl, line: 0, col: 0)
  

Local fix

Problem summary

• Since the third party oauth providers in v10 are their own
  entities that are created during migration if there are any
  custom properties in use from the original API the parameter
  substitution was not being done during migration which caused
  errors when attempting to publish the third party oauth
  providers.  This would cause any Products with APIs there were
  dependent on those third party oauth providers to also fail
  

Problem conclusion

• We are now doing the custom property parameter substitution
  within the third party oauth providers during archive:unpack of
  migration.
  

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