Support Center > Search Results > SecureKnowledge Details
Cannot establish SIC with the 3rd party vendor after creating a new OPSEC Application
Symptoms
  • Cannot establish SIC with the 3rd party vendor after creating a new OPSEC Application.
  • OPSEC 3rd party vendor reports it is unable to pull the certificate from the Security Management server.
  • The OPSEC Third Party Vendor errors may have similar errors too:

    "SIC infrastructure was unable to establish the connection to OPSEC Server [SIC_FAILURE]. SIC Error for lea: Could not retrieve CRL.."

  • alternative error messages

    "failed to fetch certificate from server"

  • Splunk Enterprise system access to R80 Manager error messages

    External Handler failed with code "1" and output 'REST ERROR[400]: Bad request - failed to fetch the certificate from the server. See splunkd.log for stderr output
Cause

OPSEC SDK does not support SHA-256 Certificates, as documented in: sk103840 - SHA-1 and SHA-256 certificates in Check Point Internal CA (ICA)


Solution
Note: To view this solution you need to Sign In .