Jan 04 2019 12:03 PM
Jan 04 2019 12:03 PM
The SecureScore web site shows that we have 31 users and 6 agents using TLS 1.0/1.1. It also provides a link to the following report site that is supposed to show me who the users and agents are:
I end up with a page that says "Please click the button to download". When I click the button, it flashes through "Downloading TLS report" and "Downloading 3DES usage report" before showing "Finished" and lovely green check mark. And absolutely nothing else. No report, no download, no instructions.
I've tried it with our own organization and a client's. I've tried multiple browsers. Same results. Has anyone had this work?
Jan 09 2019 01:12 AMSolution
I have tested this morning on Edge, Chrome and IE and experience the same.
@Ryan Heffernanis there anyone you can raise this to? We have multiple reports of community users not being able to download the TLS deprecation report on the service trust page. Nothing downloads. This seems to be a bug as users have tried several browsers including Edge, Chrome and IE. Pretty important to get this report so admins can get users off TLS 1.0/1.1.
Jan 09 2019 08:38 AM
Sorry for the problems. I'm doing some digging internally to find out who owns this site and will reply back here with an update.
Jan 09 2019 02:31 PM
Update: We've found the site owner and they are investigating the problem. Thanks for bringing it to our attention.
Jan 13 2019 05:41 PM
Thank you for reporting the issue. The engineering team is working on a fix as a high priority item. We will update this thread when this is resolved. Thank you for your patience.
Jan 14 2019 11:58 AM
Tried it again today, this time it works fine with Edge. IE still doesn't work, but I can live with that :)
Jan 16 2019 10:39 PM
Thank you for reporting the issue. Our engineering team has released a new version of our service and we added support for IE 11 and Firefox.
We have also fixed for the blank username issue. If username is '-', the service would try to find out the IP address of this record.
Please check if it works for you and thanks again for your patience.
Jan 22 2019 05:26 PM
thank you for your reply!
I have tried to download the report again but still having some problems in the username session.
Jan 22 2019 11:12 PM
Hi, thanks for the screenshot.
It could be that some users were connecting to our service before signing in, so that we are not able to identify who the user was.
We are having discussions about how we can help with this kind of situation and I'll let you know if we have any updates.
Jun 06 2019 05:13 AM
This seems to still be having issues, I was not able to download the report from Edge, however it did download from IE
unfortunately the report is blank save for the headers
Mar 11 2020 10:14 PM
We it fetches the report it basically provides the public IP address which is basically the ISP. There is no username info, instead of that it has got the public IP address.
It will be difficult to trace down what is the source. Any ideas here ?
Mar 11 2020 10:29 PM
@Mohammed Ahmed, the reason why report shows IP addresses instead of user name could be those connections were established by anonymous users or users who were not signed in. It is nearly impossible for services to tell the username when there is no user context in connection.
We could ask all users to follow the links below to disable TLS1.0/1.1 and use TLS deprecation report for investigation.