SSL Error From http issue type icon
Your SSL Icon in the URL bar of Chrome is showing up as a yellow triangle () rather than Green padlock ( ).
Clicking on the SSL icon will display the following information:
Your connection to <INSTANCE_NAME>.atlassian.net is encrypted with 128-bit encryption. However, this page includes other resources which are not secure. These resources can be viewed by others while in transit, and can be modified by an attacker to change the look of the page. The connection uses TLS 1.2. The connection is encrypted and authenticated using AES_128_GCM and uses ECDHE_RSA as the key exchange mechanism.
Use Firebug or equivalent (go to the page, view source) to inspect the page. Use text search option (Command + F mac, Control + F windows) to search for http:// on the page to identify the Insecure element. you will find something that looks like this:
<img alt="SQL Review" height="16" src="http://www.<Source_of_Image_URL>.com/images/sql-logo.png" title="SQL Review" width="16">
In this example the Image is pointing to the "SQL Review" issue type, so locate all applicable Image sources incase there are multiple.
Then Navigate to the Edit page of the speciffic Issue type to confirm the bad image is associated, the image shows an example using firebug by right clicking the image and selecting "inspect with firebug"
Issue Type Icon links to an http element from an imported issue
- First from the issue type edit screen above:
- Select the "Select Image" option
- Choose a new Icon or upload a new icon to replace the existing Icon
This Will fix any new issues but any issue Previously created will have the old insecure icon Grandfathered in so issue navigator will still show insecure:
- So to get this image updated you will have to do a bulk move to update issue type
- you can set up a temp Issue type call it something like "Temp"
- do a bulk move to Edit the issue Types to the temp issue type
then once again to move them back to the original issue type that now has the correct image file with secure element source
This is a resource intensive operation so it should be done after hours with everyone logged out except the one performing the operation.