1 of 1 people found this helpful
The client gets the CSA information in one of three ways:
1. The broker certificate on the client. It will check for the certificate first and, if it exists, uses the CSA information that the certificate contains.
2. The broker.conf.xml on the client under the broker folder. This XML is updated according to your agentbehavior xml's (agent settings).
3. The .0 certificates also contain the CSA information. When the .0 certificates are updated on the core server, the clients will automatically pull down the updated certificate when they run a security scan.
The third is likely what is happening for you. With that being said, this is working as designed. You are correct in the fact that it will search for your core server before trying to connect to the CSA however, if it does not have a broker certificate it will not connect to the CSA.
I hope this helps.