Closed as program error.
Parsing error for CA certificates owned by the company TSYS prevents the use of those certificates, and prevents us from enabling their adapters with SSP 3.x. NOTE: We ran into issues with these certificates in SSP 2.x due to the typing of Distinguished Name components as UTF8 and not PrintableString.
Provide user fix in Patch 2 update - Files: SSP3400.Patch2.tar, SSP3400cm.Patch2.tar
Users Affected: SSP administrators who attempt to import a certificate with the wrong country code encoding into the CM Problem Description: Customer attempted to import a certificate using the SSP Configuration Manager GUI and got message, Unable to parse certificate. Further research showed that the certificate was failing on the Country Code, because it had been generated with an ASN1 encoding of UTF8String instead of the required PrintableString. Platforms Affected: All
With the fix for IC81532 (RTC314325) applied the Customer may ignore the check for Illegal encoding on the Country Codes by adding the -DallowIllegalCountryNameEncodings=1 parameter to the java startup line(s) in the startCM.sh and StartEngine.sh startup scripts on UNIX. When running under Windows, add the parm to the lax.nl.java.option.additional= line in the .\bin\SSPcm$.lax file. Delivered In: 18.104.22.168,22.214.171.124,126.96.36.199,188.8.131.52 Delivered In: 184.108.40.206,220.127.116.11,18.104.22.168,22.214.171.124
Reported component name
STR SECURE PROX
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
STR SECURE PROX
Fixed component ID
Applicable component levels