[Read Me] Security Update - Supported Internet Browsers
Stephen
Hi allย ๐
ย
We wanted to give you a heads up on someย updates to our browser-based security.
ย
Wrike will be ending support of TLS (Transport Layer Security) 1.0 and 1.1 in November 2018 and will move to the more secure TLS 1.2.
ย
What does this mean, Stephen?ย ๐ค
Transport Layer Security (TLS) is a crypto protocol used to establish a secure communication channel between two systems. In other words, it's used to ensure Wrike and your chosen internet browser pass information securely and with the correct authentication.
ย
This means you need to ensure you're using a supported internet browser for the TLS 1.2 which will be rolled out in November 2018.
ย
How do I check if my browser is supported?ย ๐ป
You can confirm if you already have a supported browser,ย as listed here. You can also useย this websiteย to ensure you're using a browser that supports TLS 1.2.
ย
Note: This doesn't affect the iOS and Android mobile apps, however, mobile browsers will not be supported. Don't forget you can also use ourย Desktop app for Windows and Mac!
ย
Any questions, post below and I'll be happy to discuss further!
Hi Stephen. We use Google Chrome in iPad. How will this affect us?
Hi Melany, welcome back to the Community! We always recommend using our approved iOS or Android app which is made for mobile, including tablets and iPads. However, there's nothing to worry about here; Chrome for iPad supports our new securityย update so you shouldn't have any issues.
Thanks ๐
Thank you for keeping the product secure.
Hello,
Does TLS 1.0 and 1.1 need to be disabled on the browser that is connecting to Wrike or will it work as long as TLS 1.2 is enabled?ย
ย I was so glad to see your comment, Stephen, to Melany that chrome on the iPad will still work. Being able to use the desktop app on the iPad is absolutely critical to our workflow. The mobile app is just not functional or stable enough. ย I am hoping that will change, but for the time being we will run the program in desktop mode (using request desktop site) on the mobile chrome browser when weโre not at our desktops.
Hi Stephen,
I am trying to fetch my Wrike data through .Net code and it is working great as of now.
I am making use of in-built functions provided by Microsoft at System.dll ( version 4.0.30319.1).
Will stopping support to TLS 1.0 & 1.1, affect me ?
ย
Thankyou !
@Ansel - ๐
@Jerry -ย All recent versions of Edge, Chrome, Firefox, and Safari are pre-configured to use TLS 1.2 by default. There is no need to disable TLS 1.0 and 1.1 on those browsers. The most vulnerable browser is Internet Explorer 10 (and embedded browsers on systems running it) It is set by default to use TLS 1.1 You must ensure that browsers are configured to use TLS 1.2 ๐
@Tony, thanks for your feedback on mobile. It's an area we constantly review for and enhance so please so continue to review it and provide feedback here. Perhaps starting to any ideas to this existing feedback post.
@Ruchin -ย Iโm afraid this update will affect your code. As far as I know according to the msdn.microsoft.com: โ.NET Framework 4.0 does not have the TLS 1.2 or TLS 1.1. To use TLS 1.2, you must use .NET Framework 4.5.ย The common suggestion for developers is to use the latest version of the framework. As I say .NET Framework 4.5 supports TLS 1.2. If you need further support, I can raise a ticket to our Support Team to discuss, please let me know ๐
@stephen You're welcome. I must say that the recently-added ability to add a project on mobile was an important step in the right direction. And, symbolically, shows that development is happening. I'll put any additional ideas or feedback into the postย to which you linked.
Thanks Stephen for the input,
I would be gratefulย if you can connect me to your support team as well via a ticket.
I find an article (https://blogs.perficient.com/2016/04/28/tsl-1-2-and-net-support/) which says :
for NET 4.0.ย TLS 1.2 is not supported, but if you have .NET 4.5 (or above) installed on the system then you still can opt in for TLS 1.2 even if your application framework doesnโt support it. The only problem is that SecurityProtocolType in .NET 4.0 doesnโt have an entry for TLS1.2, so weโd have to use a numerical representation of this enum value:
I am not sure if this would be a good solution for my case.
I feel like giving a try at it and then testing my app at some non-production system if available, which would resemble the release of Nov1.
@stephen Thank you so much for the information, very clear and of great value.ย Let me take advantage to comment that using the IOs App we can not modify the zoom of the screen, as we use to do using Chrome. Do you know if it is possible to do? If not, could youย bear in mind this issue in the next updates? Many thanks for everything!!ย ย ย
As of today - my Office Timeline plus add in will not connect to wrike any longer.ย Help.ย I have 10+ gantt charts that I need to have in PPT by next Monday.ย Receiving an error about setting the web proxy.ย This worked fine 2 days ago.
Hi Karen, Welcome to the Community!
The Support Team would need to take a closer look for you. I've raised a ticket for you and you'll get an email notification of this soon ๐
Hi Stephen,
ย
My team and I are also experiencing the same slowdown/no connection Wrike since this TLS update. I believe the TLS is related. We have all enabled TLS 1.2 in our browsers. I'm on an Macbook Air, and Wrike for me is extremely slow but it does load. For my teammates, who are on PCs, Wrike hardly loads.ย
ย
Can you also raise a ticket for me? This problems seems to be affecting many of Wrike's users--and it's a big problem right now.
Hi Nhat, I'm not sure that this should be causing an issue however the Support Team will be able to investigate. I've raised a ticket for you now and you'll receive confirmation of this by email.
Thanks for posting ๐