A fix is available
APAR status
Closed as program error.
Error description
After, migrating API to the v5 policy emulation, API Calls fail with the error "unable to get TLS Profile '{profile-name}:{version}'" even though the TLS client profile object exists in DataPower gateway
Local fix
Manually put full DP object name of tls-profile in the API.
Problem summary
API gateway may not provide access to TLS profile information for the organization despite SSL Client Profile in DataPower existing.
Problem conclusion
Fix is available in 10.0.1.1
Temporary fix
Comments
APAR Information
APAR number
IT34769
Reported component name
DATAPOWER
Reported component ID
DP1234567
Reported release
A0X
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-11-03
Closed date
2020-11-18
Last modified date
2020-11-18
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
RA0X PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateways"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A0X"}]
Document Information
Modified date:
25 August 2021