IT42165: INSECURE OPTION IN TLS CLIENT PROFILE IS NOT BEHAVING THE SAME IN V10 AS IN V5

APAR status

• Closed as program error.

Error description

• In API Connect v5, when "Allow insecure server connection" is
  enabled in v5, it overrides Truststore setting on the gateway,
  i.e. "Validate server certificate" is set to "off" on Datapower
  for this TLS Client Profile, no matter if Truststore is set or
  not.
  
  In API Connect v10, this is working the other way around - when
  "Allow insecure server connection" is enabled, and also
  Truststore is set, the resulting TLS Client Profile on DataPower
  Gateway ignores "Allow insecure server connection" and sets
  "Validate server certificate" setting to "on" and uses
  respective validation credentials.
  

Local fix

Problem summary

• Insecure option in TLS Client profile exhibits different
  behavior in v10 compared to v5.
  

Problem conclusion

• Fix is available in 10.5.0.3, 10.0.1.11 and 2018.4.1.24.
  
  For a list of the latest fix packs available, please see:
  https://www.ibm.com/support/pages/node/83105
  

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

  DATAPOWER

• Fixed component ID

  DP1234567

Applicable component levels