- ago
Looks like you're using an old version of the TLS cipher that Azure no longer honors. (I didn't know the WL6 website was hosted on Azure.) Here's the WL6 website error:

CODE:
Server Error in '/' Application. {"error":"invalid_request","error_description":"AADSTS1002016: You are using TLS version 1.0, 1.1 and/or 3DES cipher which are deprecated to improve the security posture of Azure AD. Your TenantID is: 795d52b6-5c44-4aa4-b3fa-c43718dc1460. Please refer to <a href="https://go.microsoft.com/fwlink/?linkid=2161187" target="_blank">https://go.microsoft.com/fwlink/?linkid=2161187</a> and conduct needed actions to remediate the issue. For further questions, please contact your administrator.\r\nTrace ID: 1319cb92-d5d6-4b7c-8246-b34368210801\r\nCorrelation ID: ca719def-5566-4faa-9b5c-c366e0b17488\r\nTimestamp: 2022-08-03 13:44:58Z","error_codes":[1002016],"timestamp":"2022-08-03 13:44:58Z","trace_id":"1319cb92-d5d6-4b7c-8246-b34368210801","correlation_id":"ca719def-5566-4faa-9b5c-c366e0b17488"} Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Exception: {"error":"invalid_request","error_description":"AADSTS1002016: You are using TLS version 1.0, 1.1 and/or 3DES cipher which are deprecated to improve the security posture of Azure AD. Your TenantID is: 795d52b6-5c44-4aa4-b3fa-c43718dc1460. Please refer to <a href="https://go.microsoft.com/fwlink/?linkid=2161187" target="_blank">https://go.microsoft.com/fwlink/?linkid=2161187</a> and conduct needed actions to remediate the issue. For further questions, please contact your administrator.\r\nTrace ID: 1319cb92-d5d6-4b7c-8246-b34368210801\r\nCorrelation ID: ca719def-5566-4faa-9b5c-c366e0b17488\r\nTimestamp: 2022-08-03 13:44:58Z","error_codes":[1002016],"timestamp":"2022-08-03 13:44:58Z","trace_id":"1319cb92-d5d6-4b7c-8246-b34368210801","correlation_id":"ca719def-5566-4faa-9b5c-c366e0b17488"}
0
540
Solved
4 Replies

Closed

Bookmark

Sort
- ago
#1
This is a known issue caused by a breaking change at Microsoft Azure.
0
- ago
#2
I don't care about the WL6 website, but I need to authenticate the WL6 client since it's still my primary trading platform. If you could fix the WL6 authentication part soon, that would be good.
0
Glitch8
 ( 10.94% )
- ago
#3
We're working on it!
1
Best Answer
- ago
#4
Fixed by our webmaster.
1

Closed

Bookmark

Sort