Answer by Matthew E. ·
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.
Answer by Babar Q. ·
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.
CAS/ADS Server Configuration Automation 3 Answers
As part of security overhaul, my client wants to have a 2-factor authentication in DCRUM. This 2-factor authentication should be valid when accessing CAS, ADS and RUM Console. Is it possible presently ? What are my options ? 1 Answer
Link an ADS Report to a CAS Report 2 Answers