IJ54644: WACERT020E THE CERTIFICATE OR KEY "/TWSDATA/USR/SERVERS/ENGINESERVER/RESOURCES/SECURITY/TLS.CRT" IS NOT IN A VALID PEM FORMAT

10.2.5-IWS_QSG
10.2.5-IWS-DOCKER-AI_DATA_ADVISOR-LNX_Z
10.2.5-IWS-DOCKER-AI_DATA_ADVISOR-LNX_X86_64
10.2.5-IWS-DOCKER-ZAGENT-LNX_Z
10.2.5-IWS-DOCKER-ZAGENT-LNX_X86_64
10.2.5-IWS-DOCKER-AGENT-LNX_Z
10.2.5-IWS-DOCKER-AGENT-LNX_X86_64
10.2.5-IWS-DOCKER-FILEPROXY-LNX_Z
10.2.5-IWS-DOCKER-FILEPROXY_LNX_X86_64
10.2.5-IWS-DOCKER-CONSOLE-LNX_Z
10.2.5-IWS-DOCKER-CONSOLE-LNX_X86_64
10.2.5-IWS-DOCKER-SERVER-LNX_Z
10.2.5-IWS-DOCKER-SERVER-LNX_X86_64
10.2.5-IWS-OCLI-WINDOWS
10.2.5-IWS-OCLI-MAC_x86
10.2.5-IWS-OCLI-MAC_ARM
10.2.5-IWS-OCLI-LNX_X86_64
10.2.5-IWS-BATCH_REPORT-Z_USS
10.2.5-IWS-BATCH_REPORT-WINDOWS
10.2.5-IWS-BATCH_REPORT-LNX_Z
10.2.5-IWS-BATCH_REPORT-LNX_X86_64
10.2.5-IWS-FILEPROXY-WINDOWS
10.2.5-IWS-FILEPROXY-LNX_Z
10.2.5-IWS-FILEPROXY-LNX_X86_64
10.2.5-IWS-CONSOLE-Z_USS.pax
10.2.5-IWS-CONSOLE-WINDOWS
10.2.5-IWS-CONSOLE-LNX_Z
10.2.5-IWS-CONSOLE-LNX_X86_64
10.2.5-IWS-CONSOLE-AIX
10.2.5-IWS-ZAGENT-WINDOWS
10.2.5-IWS-ZAGENT-LNX_Z
10.2.5-IWS-ZAGENT-LNX_X86_64
10.2.5-IWS-ZAGENT-IBMi
10.2.5-IWS-ZAGENT-AIX
10.2.5-IWS-SERVER-WINDOWS
10.2.5-IWS-SERVER-LNX_Z
10.2.5-IWS-SERVER-LNX_X86_64
10.2.5-IWS-SERVER-AIX
10.2.5-IWS-AGENT-WINDOWS
10.2.5-IWS-AGENT-LNX_Z
10.2.5-IWS-AGENT-LNX_X86_64
10.2.5-IWS-AGENT-IBMi
10.2.5-IWS-AGENT-AIX

APAR status

• Closed as documentation error.

Error description

• From the process Performing a direct upgrade from v 9.5.0.x or v
  10.x.x to v 10.2.3
  
  https://www.ibm.com/docs/en/workload-automation/10.2.3?topic=uf
  c-performing-direct-upgrade-from-v-950x-10xx-v-1023
  
  
  Where 1) Converting default certificates
  https://www.ibm.com/docs/en/workload-automation/10.2.3?topic=10
  23-converting-default-certificates
  
  
  Where steps 4 and 5 talking about <private_key> and <public_key>
  from tls.tot
  
  4)The tls.key file must be structured as follows:
  
  5)The tls.crt file must be structured as follows:
  
  
  ----BEGIN ENCRYPTED PRIVATE KEY----
  ----END ENCRYPTED PRIVATE KEY----
  
  
  Issue: tls.tot actually has 5 hyphens (-----), whereas above
  suggested structure has 4 hyphens (----) which causing the issue
  
  
  While Upgrading the DWC fails with this error
  WACERT020E The certificate or key "/home/twsuser/IBM/WA/TWSDATA
  /usr/servers/engineServer/resources/security/tls.crt"is not in a
  

Local fix

• Solution to customer has provided adding missing - hyphen into
  tls.key and tls.crt file
  
  The missing hyphen character on either side of the words causes
  the file to be identified as type ASCII.
  
  
  On Linux systems the 'file' command can be used to determine the
  file type.  For example:
  
  
  > file resources/security/ca.crt
  
  resources/security/ca.crt: ASCII text
  
  
  
  ...after adding the missing '-' chars:
  
  
  
  > file resources/security/ca.crt
  
  resources/security/ca.crt: PEM certificate
  

Problem summary

• The documentation will be modified to fix the problem
  

Problem conclusion

• The fix for the APAR will be delivered in 10.2.5 documentation
  

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

Applicable component levels