IBM Support

Corrupted APIKEY after upgrade MAS or execute a backflow

Troubleshooting


Problem

During the upgrade of Manage, the APIKEY values in apikeytoken table can become corrupted, affecting the integration and User synchronization process between MAS and Manage.

Symptom

In the usersync pod log, an error can be seen:
 
  • 2022-09-12 05:17:34,417 usersync-agent-manage INFO [nexertest maxadmin] Sync user response: r.status: 400, r.text: Error 400: BMXAA9549E - The API key token is invalid. Either the token may have expired or the token has been revoked by the administrator.
 
Using the OLSC/REST api with an apikey, an error is returned from the client request:
 
  • Error: BMXAA1649E - A programming error resulted in a null pointer exception
 
 

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m50000000CbFGAA0","label":"Integration"}],"ARM Case Number":"TS010887777","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.8.0"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
17 October 2022

UID

ibm16829527