I believe this has the information for securing the communication from the CAS and ADS:
Thank you for your reply.
I had gone through with the same link before posting the question because I was confused about the statement that 'Set up the report server to use secure connections with users' web browsers and to use automatically generated data or your own keys and certificates'.
Therefore, I wanted to know that is there any difference between 'Console' and 'Browsers' connectivity over the SSL.
There is a difference.
Originally users would connect to the CAS for reporting reasons on port 80 using HTTP. In newer versions, I believe the default changed to 443 SSL. So the quoted text above is referring to that.
In v17 the RUM Console was integrated into the CAS, instead of being a separate software component so to speak. This will also be using SSL over 443 as you access it in a similar way to the reports (now at least).
Finally, you have the AMDs which send data back to the CAS and can be configured in the RUM Console. Both of these now, I believe, uses 443 or at least it can,
So yes, there is a difference when they speak of Console vs Browsers connectivity and what you'll find is that the newer or newest versions of the product will use SSL on 443 for almost all comms.
Now I understood that the version we have in our environment communicate only over the HTTP between 'Console' and 'Reporting Servers' but in the latest version (2017 release) all the communications designed over the SSL.