LI81621: THE TOKEN AND TOKEN_EXPIRATION ARE NOT CLEARED UP ON DEVELOPER PORTAL RESTORE

APAR status

• Closed as program error.

Error description

• When restoring a portal service or portal site, the token and
  token_expiration fields of the respective portal.service or
  portal.uuid records in the Database are not cleared.
  As a result, if you perform a restore, an old token (sill
  within the expiry time) is restored in the portal database but
  when the token is used by the developer portal to communicate
  with the management server, it is rejected.
  

Local fix

• You can force the token to be set to null so that the next time
  the developer portal tries to synchronize with the management
  server it will get a new token.
  This can be done by performing the steps below:
  1- Exec to the admin www-pod container with the command:
  -> kubectl exec -ti  -c admin bash
  2- list the sites with the command:
  -> list_sites
  You get for example:
  a4a8ef28-5f4a-40ec-b176-e2230a5644ea.023f3286-1e24-48b4-beda-5ca
  9919bb74f => portal_endpoint/myorg/mycat (INSTALLED)
  3- Resetting the client id and secret to null for the problem
  restored site with the command
  -> mysql -e 'update portal.uuid set client_id=null,
  client_secret=null where
  uuid="a4a8ef28-5f4a-40ec-b176-e2230a5644ea.023f3286-1e24-48b4-be
  da-5ca9919bb74f"'
  4- Force a refreshing of the content for restored site using
  the command:
  -> site_content_refresh -f
  a4a8ef28-5f4a-40ec-b176-e2230a5644ea.023f3286-1e24-48b4-beda-5ca
  9919bb74f
  

Problem summary

• When restoring a Developer Portal site into a running
  environment, errors such as the following may be observed from
  the restore job:
  Completion with a status "error" - command "list_sites" showed "
  Webhooks not configured" for the restored site.
  
  When restoring a Developer portal service or Developer portal
  site, the token and token_expiration fields of the respective
  portal.service or portal.uuid records in the Developer Portal
  database were not bing cleared.
  
  As a result of the restore, an old token (still within the
  expiry time) is restored in the Developer Portal database but
  when the token is used by the Developer Portal to communicate
  with the Management Server, it is rejected.
  

Problem conclusion

• The issue is addressed in API Connect 2018.4.1.13 and targeted
  for inclusion in version 10.0.1.
  

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

• R18X PSY

     UP