Forum Discussion

iangoodale's avatar
iangoodale
Copper Contributor
Jan 04, 2019
Solved

TLS Deprecation Report always empty

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:   ...
  • ChrisHoardMVP's avatar
    ChrisHoardMVP
    Jan 09, 2019

    Hi Iangoodale,

     

    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.

     

    Best, Chris

Ryan Heffernan's avatar
Ryan Heffernan
Icon for Microsoft rankMicrosoft
Jan 09, 2019

Update: We've found the site owner and they are investigating the problem. Thanks for bringing it to our attention. 

AdminLiz's avatar
AdminLiz
Copper Contributor
Jan 17, 2019

Hi, I download a TLS report and found that the username is blank, could you please check it for me?

  • jiaden's avatar
    jiaden
    Copper Contributor
    Jan 17, 2019

    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.

    • AdminLiz's avatar
      AdminLiz
      Copper Contributor
      Jan 23, 2019

      thank you for your reply!

      I have tried to download the report again but still having some problems in the username session.

      • jiaden's avatar
        jiaden
        Copper Contributor
        Jan 23, 2019

        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.

    • iangoodale's avatar
      iangoodale
      Copper Contributor
      Jan 17, 2019

      Looks like it's working now. Thanks for getting this fixed!

Resources