Claroty integration

[AdamRejmandowsk]

Hi, I’m trying to connect Claroty CTD version 4.7.1.44813 with Checkpoint R82. Are there any known issues with these connections? Claroty is directly connected to the network under CheckPoint, and the connections can be seen in TCPdump. Upon the first connection attempt, an untrusted certificate error appears. The certificate is accepted, and in the next step, the message shown in the screenshot appears. The password is definitely correct. Do you have any idea? 

[AntoinetteHodes]

Hi Adam, are you sure the port is correct? It really seems that either the password or the port is definitely incorrect. Could you share the configuration of the Claroty instance? Otherwise please reach out to your local expert to help fix this issue. 

[AdamRejmandowsk]

Thank you for your response. I can confirm that all the suggestions have been verified. I am confident that both the password and the port are correct.

[Chris_Atkinson]

Is the hostname correct and resolvable? The port nowadays should be 443 (previously was 9000)

CTD uses the older style Identity Awareness integration whereas xDome will connect to IoT Protect via the Infinity portal.

[AdamRejmandowsk]

Of course, it is configured in the hosts file.

[Chris_Atkinson]

Please try <ip_or_fqdn>/checkpoint-api/

e.g. claroty/checkpoint-api/

[AdamRejmandowsk]

Thank you for your attempt to help, but your advice did not resolve the issue.