IJ35668: REVOKE COMMAND REQUIRED EVEN AFTER AN APIKEY EXPIRES

APAR status

• Closed as program error.

Error description

• PROBLEM DESCRIPTION:
  
  Even after expiring there is no way to create a new apikey for
  the same userid, a revoke is still required.
  
  
  PERFORMANCE ISSUE: NO
  
  
  STEPS TO REPRODUCE:
  
  1.) POST maximourl/maximo/oslc/os/mxapiapikey?lean=1
  
  {
  "expiration":"1",
  "userid":"maxadmin"
  }
  
  Key should be created successfully.
  
  2.) Immediatly try to create another one for the same userid:
  
  "message": "iface#onekeyperuser"
  
  3.) Wait until key is expired and try to create a new one:
  
  "message": "iface#onekeyperuser"
  
  RESULTS:
  
  Even after expiring the apikey, user must use revoke command in
  order to create a new one.
  
  EXPECTED RESULTS:
  
  Once expired, the user should be able to create a new apikey
  immediately.
  
  
  PRODUCT VERSION:
  IBM Tpae Integration Framework 7.6.1.2
  

Local fix

Problem summary

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package: | Release 7.6.1.3 of Base Services
  

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

  INTEGRATION

• Fixed component ID

  5724R46I1

Applicable component levels