Provider Hosted App (PHA) application errors (TLS errors and 401 errors).

Published 04-14-2021 06:27 PM 3,554 Views
Microsoft

Note: Please take extreme caution before making any changes in Production. Make sure you test the changes in a test environment first.

 

Recently due to a spate of updates to various endpoints in SharePoint, Azure, and the AAD auth login endpoints, we are seeing projects compiled with version of .NET before 4.6 cause TLS errors which don’t always show as TLS errors in the PHA. They are intermittent sometimes due to the updating of load balanced servers. In PHAs, it sometimes shows as a 401 error due to the way the token helper PHA code works. The actual error is this:

 

"The underlying connection was closed” or “System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host”

This error is most likely due to deprecation of TLS1 1.0 & 1.1 while .NET 4.5 apps don't use TLS 1.2 without an explicit code change.

Please see:

Preparing for TLS 1.2 in Office 365 and Office 365 GCC - Microsoft 365 Compliance | Microsoft Docs

Enable TLS 1.2 on servers - Configuration Manager | Microsoft Docs

TLS 1.0 and 1.1 deprecation - Microsoft Tech Community

Transport Layer Security (TLS) best practices with the .NET Framework | Microsoft Docs

 

The updates were communicated in the Office 365 message center.

  • MC218794 - July 17, 2020 | TLS 1.0 and 1.1 retirement date in Office 365 to be October 15, 2020
  • MC240160 - Feb 16, 2021 | Reminder: Disabling TLS 1.0 and TLS 1.1 in Microsoft 365

The deprecation of TLS 1.0 and 1.1 on all SharePoint Online servers will be completed by June of 2021. There are no rollbacks to this security update.

 

Scenarios

In all scenarios on a VM or physical server

you need to add the following registry key settings on your apps web server(s):

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]

"SystemDefaultTlsVersions" = dword:00000001

"SchUseStrongCrypto" = dword:00000001

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]

"SystemDefaultTlsVersions" = dword:00000001

"SchUseStrongCrypto"=dword:00000001

 

Note: You will need to restart your server(s)

 

If the App web is hosted on Azure

Log into the Azure portal (portal.azure.com) with an account with admin rights on the web app in question.

Once you open the App Services and select the web app hosting the PHA site, click on the App Service Editor (Preview).

SPDev_Support_0-1618449668859.png

 

This will open the editor, then select the web.config file and change the circled targetFramework attribute to 4.7 preferably (any setting higher than 4.6 will work too). Note the status in the upper right will say ‘DIRTY’ for a bit, then it should auto-save and change back to ‘SAVED’-

SPDev_Support_1-1618449668895.png

 

At this point you should be set, refresh the page with the PHA and all should be good.

 

If your application is an Azure web job, Executable (e.g. console, WPF, Windows Forms, etc.), or WCF service

The .NET registry keys mentioned above need to be applied on the host machine that runs the application (except for the Azure case).

Then the application project in Visual Studio needs to be retargeted to 4.6+ (4.7.1+ recommended) by changing the target framework setting in the application properties and re-compiling. The Azure web job executable will need to be updated with the re-compiled executable.

 

More here-

Targeted .NET frameworks - Visual Studio | Microsoft Docs

 

If you want to read up on known issues for specific re-targeting scenarios, you can select the from/to versions and see the known issues-

Runtime and retargeting changes - .NET Framework | Microsoft Docs

 

Note: You can’t use the config file for the exe to re-target the same way we can for a web application.

 

If you are running an app on Java
You can find more information here- 
3 Comments
New Contributor

Is this something that would be intermittent? Or would it be something that once it breaks ends up being constant? As well, in the HTTP response body is there any message indicating the cause as TLS so we can verify if this is indeed the issue?

Microsoft

Yes. We have seen this would be both intermittent and constant. In the response body "The underlying connection was closed: An unexpected error occurred on a send." is the most consistent message we have seen. We have also seen Tls stream error messages in the stack trace.

Microsoft

Make sure to put in the strong crypto key for 64 and 32 bit compilation, as VS projects default to prefer 32 bit, and if that key is missing (the Wow6432Node one), those programs will still use the older TLS-
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

%3CLINGO-SUB%20id%3D%22lingo-sub-2297729%22%20slang%3D%22en-US%22%3ERe%3A%20Provider%20Hosted%20App%20(PHA)%20application%20errors%20(TLS%20errors%20and%20401%20errors).%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2297729%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20this%20something%20that%20would%20be%20intermittent%3F%20Or%20would%20it%20be%20something%20that%20once%20it%20breaks%20ends%20up%20being%20constant%3F%20As%20well%2C%20in%20the%20HTTP%20response%20body%20is%20there%20any%20message%20indicating%20the%20cause%20as%20TLS%20so%20we%20can%20verify%20if%20this%20is%20indeed%20the%20issue%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2300066%22%20slang%3D%22en-US%22%3ERe%3A%20Provider%20Hosted%20App%20(PHA)%20application%20errors%20(TLS%20errors%20and%20401%20errors).%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2300066%22%20slang%3D%22en-US%22%3E%3CP%3EYes.%20We%20have%20seen%20this%20would%20be%20both%20intermittent%20and%20constant.%20In%20the%20response%20body%20%22%3CSPAN%3EThe%20underlying%20connection%20was%20closed%3A%20An%20unexpected%20error%20occurred%20on%20a%20send.%3C%2FSPAN%3E%22%20is%20the%20most%20consistent%20message%20we%20have%20seen.%20We%20have%20also%20seen%20Tls%20stream%20error%20messages%20in%20the%20stack%20trace.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2304635%22%20slang%3D%22en-US%22%3ERe%3A%20Provider%20Hosted%20App%20(PHA)%20application%20errors%20(TLS%20errors%20and%20401%20errors).%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2304635%22%20slang%3D%22en-US%22%3E%3CP%3EMake%20sure%20to%20put%20in%20the%20strong%20crypto%20key%20for%2064%20and%2032%20bit%20compilation%2C%20as%20VS%20projects%20default%20to%20prefer%2032%20bit%2C%20and%20if%20that%20key%20is%20missing%20(the%20Wow6432Node%20one)%2C%20those%20programs%20will%20still%20use%20the%20older%20TLS-%3CBR%20%2F%3EWindows%20Registry%20Editor%20Version%205.00%3CBR%20%2F%3E%5BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5C.NETFramework%5Cv4.0.30319%5D%3CBR%20%2F%3E%22SchUseStrongCrypto%22%3Ddword%3A00000001%3CBR%20%2F%3E%5BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CWow6432Node%5CMicrosoft%5C.NETFramework%5Cv4.0.30319%5D%3CBR%20%2F%3E%22SchUseStrongCrypto%22%3Ddword%3A00000001%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273611%22%20slang%3D%22en-US%22%3EProvider%20Hosted%20App%20(PHA)%20application%20errors%20(TLS%20errors%20and%20401%20errors).%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273611%22%20slang%3D%22en-US%22%3E%3CP%3E%3CFONT%20color%3D%22%23FF0000%22%3E%3CU%3E%3CSTRONG%3ENote%3A%20Please%20take%20extreme%20caution%20before%20making%20any%20changes%20in%20Production.%20Make%20sure%20you%20test%20the%20changes%20in%20a%20test%20environment%20first.%3C%2FSTRONG%3E%3C%2FU%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERecently%20due%20to%20a%20spate%20of%20updates%20to%20various%20endpoints%20in%20SharePoint%2C%20Azure%2C%20and%20the%20AAD%20auth%20login%20endpoints%2C%20we%20are%20seeing%20projects%20compiled%20with%20version%20of%20.NET%20before%204.6%20cause%20TLS%20errors%20which%20don%E2%80%99t%20always%20show%20as%20TLS%20errors%20in%20the%20PHA.%20They%20are%20intermittent%20sometimes%20due%20to%20the%20updating%20of%20load%20balanced%20servers.%20In%20PHAs%2C%20it%20sometimes%20shows%20as%20a%20401%20error%20due%20to%20the%20way%20the%20token%20helper%20PHA%20code%20works.%20The%20actual%20error%20is%20this%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%22The%20underlying%20connection%20was%20closed%E2%80%9D%20or%20%E2%80%9CSystem.Net.Sockets.SocketException%3A%20An%20existing%20connection%20was%20forcibly%20closed%20by%20the%20remote%20host%E2%80%9D%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThis%20error%20is%20most%20likely%20due%20to%20deprecation%20of%20TLS1%201.0%20%26amp%3B%201.1%20while%20.NET%204.5%20apps%20don't%20use%20TLS%201.2%20without%20an%20explicit%20code%20change.%3C%2FP%3E%0A%3CP%3EPlease%20see%3A%3C%2FP%3E%0A%3CP%3E%3CU%3E%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252Fmicrosoft-365%252Fcompliance%252Fprepare-tls-1.2-in-office-365%253Fview%253Do365-worldwide%26amp%3Bdata%3D04%257C01%257Cmamcv%2540microsoft.com%257C1b4a0173e21c454a5e6b08d8f4780658%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637528143640405393%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C1000%26amp%3Bsdata%3DDSWr33W1sSz%252FP9jJK3YzZdXyPFbb9dZ9ncmkemZKTE0%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EPreparing%20for%20TLS%201.2%20in%20Office%20365%20and%20Office%20365%20GCC%20-%20Microsoft%20365%20Compliance%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FU%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmem%2Fconfigmgr%2Fcore%2Fplan-design%2Fsecurity%2Fenable-tls-1-2-server%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EEnable%20TLS%201.2%20on%20servers%20-%20Configuration%20Manager%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-sharepoint-blog%2Ftls-1-0-and-1-1-deprecation%2Fba-p%2F1620264%22%20target%3D%22_blank%22%3ETLS%201.0%20and%201.1%20deprecation%20-%20Microsoft%20Tech%20Community%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdotnet%2Fframework%2Fnetwork-programming%2Ftls%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ETransport%20Layer%20Security%20(TLS)%20best%20practices%20with%20the%20.NET%20Framework%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20updates%20were%20communicated%20in%20the%20Office%20365%20message%20center.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EMC218794%20-%20July%2017%2C%202020%20%7C%20TLS%201.0%20and%201.1%20retirement%20date%20in%20Office%20365%20to%20be%20October%2015%2C%202020%3C%2FLI%3E%0A%3CLI%3EMC240160%20-%20Feb%2016%2C%202021%20%7C%20Reminder%3A%20Disabling%20TLS%201.0%20and%20TLS%201.1%20in%20Microsoft%20365%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EThe%20deprecation%20of%20TLS%201.0%20and%201.1%20on%20all%20SharePoint%20Online%20servers%20will%20be%20completed%20by%20%3CU%3EJune%20of%202021%3C%2FU%3E.%20There%20are%20no%20rollbacks%20to%20this%20security%20update.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3E%3CSTRONG%3EScenarios%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CU%3E%3CSTRONG%3EIn%20all%20scenarios%20on%20a%20VM%20or%20physical%20server%3C%2FSTRONG%3E%3C%2FU%3E%3C%2FP%3E%0A%3CP%3Eyou%20need%20to%20add%20the%20following%20registry%20key%20settings%20on%20your%20apps%20web%20server(s)%3A%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2011.0pt%3B%22%3E%3CSPAN%20style%3D%22font-weight%3A%20bold%3B%22%3E%5BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5C.NETFramework%5Cv4.0.30319%5D%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2011.0pt%3B%22%3E%3CSPAN%20style%3D%22font-weight%3A%20bold%3B%22%3E%22SystemDefaultTlsVersions%22%20%3D%20dword%3A00000001%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2011.0pt%3B%22%3E%3CSPAN%20style%3D%22font-weight%3A%20bold%3B%22%3E%22SchUseStrongCrypto%22%20%3D%20dword%3A00000001%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2011.0pt%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2011.0pt%3B%22%3E%3CSPAN%20style%3D%22font-weight%3A%20bold%3B%22%3E%5BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CWow6432Node%5CMicrosoft%5C.NETFramework%5Cv4.0.30319%5D%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2011.0pt%3B%22%3E%3CSPAN%20style%3D%22font-weight%3A%20bold%3B%22%3E%22SystemDefaultTlsVersions%22%20%3D%20dword%3A00000001%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2011.0pt%3B%22%3E%3CSPAN%20style%3D%22font-weight%3A%20bold%3B%22%3E%22SchUseStrongCrypto%22%3Ddword%3A00000001%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2011.0pt%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2011.0pt%3B%22%3E%3CSPAN%20style%3D%22font-weight%3A%20bold%3B%20text-decoration%3A%20underline%3B%22%3ENote%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-weight%3A%20bold%3B%22%3E%3A%20You%20will%20need%20to%20restart%20your%20server(s)%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CU%3EIf%20the%20App%20web%20is%20hosted%20on%20Azure%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3ELog%20into%20the%20Azure%20portal%20(portal.azure.com)%20with%20an%20account%20with%20admin%20rights%20on%20the%20web%20app%20in%20question.%3C%2FP%3E%0A%3CP%3EOnce%20you%20open%20the%20App%20Services%20and%20select%20the%20web%20app%20hosting%20the%20PHA%20site%2C%20click%20on%20the%20App%20Service%20Editor%20(Preview).%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22SPDev_Support_0-1618449668859.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F272955i28EF830997DC2E5F%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22SPDev_Support_0-1618449668859.png%22%20alt%3D%22SPDev_Support_0-1618449668859.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20will%20open%20the%20editor%2C%20then%20select%20the%20%3CSTRONG%3Eweb.config%3C%2FSTRONG%3E%20file%20and%20change%20the%20circled%20%3CSTRONG%3EtargetFramework%3C%2FSTRONG%3E%20attribute%20to%204.7%20preferably%20(any%20setting%20higher%20than%204.6%20will%20work%20too).%20Note%20the%20status%20in%20the%20upper%20right%20will%20say%20%E2%80%98%3CSTRONG%3EDIRTY%3C%2FSTRONG%3E%E2%80%99%20for%20a%20bit%2C%20then%20it%20should%20auto-save%20and%20change%20back%20to%20%E2%80%98%3CSTRONG%3ESAVED%3C%2FSTRONG%3E%E2%80%99-%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22SPDev_Support_1-1618449668895.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F272954iBDD403B49258F7B8%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22SPDev_Support_1-1618449668895.png%22%20alt%3D%22SPDev_Support_1-1618449668895.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAt%20this%20point%20you%20should%20be%20set%2C%20refresh%20the%20page%20with%20the%20PHA%20and%20all%20should%20be%20good.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CU%3EIf%20your%20application%20is%20an%20Azure%20web%20job%2C%20Executable%20(e.g.%20console%2C%20WPF%2C%20Windows%20Forms%2C%20etc.)%2C%20or%20WCF%20service%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20.NET%20registry%20keys%20mentioned%20above%20need%20to%20be%20applied%20on%20the%20host%20machine%20that%20runs%20the%20application%20(except%20for%20the%20Azure%20case).%3C%2FP%3E%0A%3CP%3EThen%20the%20application%20project%20in%20Visual%20Studio%20needs%20to%20be%20retargeted%20to%204.6%2B%20(4.7.1%2B%20recommended)%20by%20changing%20the%20target%20framework%20setting%20in%20the%20application%20properties%20and%20re-compiling.%20The%20Azure%20web%20job%20executable%20will%20need%20to%20be%20updated%20with%20the%20re-compiled%20executable.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMore%20here-%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fvisualstudio%2Fide%2Fvisual-studio-multi-targeting-overview%3Fview%3Dvs-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ETargeted%20.NET%20frameworks%20-%20Visual%20Studio%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20want%20to%20read%20up%20on%20known%20issues%20for%20specific%20re-targeting%20scenarios%2C%20you%20can%20select%20the%20from%2Fto%20versions%20and%20see%20the%20known%20issues-%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdotnet%2Fframework%2Fmigration-guide%2Fapplication-compatibility%3Fredirectedfrom%3DMSDN%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ERuntime%20and%20retargeting%20changes%20-%20.NET%20Framework%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CU%3E%3CSTRONG%3ENote%3C%2FSTRONG%3E%3C%2FU%3E%3A%20You%20can%E2%80%99t%20use%20the%20config%20file%20for%20the%20exe%20to%20re-target%20the%20same%20way%20we%20can%20for%20a%20web%20application.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CDIV%3E%3CSTRONG%3E%3CU%3EIf%20you%20are%20running%20an%20app%20on%20Java%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FDIV%3E%0A%3CDIV%3EYou%20can%20find%20more%20information%20here-%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%3CA%20href%3D%22https%3A%2F%2Fwww.java.com%2Fen%2Fconfigure_crypto.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EConfigure%20Oracle's%20JDK%20and%20JRE%20Cryptographic%20Algorithms%20(java.com)%3C%2FA%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2273611%22%20slang%3D%22en-US%22%3E%3CP%3EProvider%20Hosted%20App%20(PHA)%20application%20errors%20(TLS%20errors%20and%20401%20errors).%20%E2%80%9CThe%20underlying%20connection%20was%20closed%E2%80%9D%20or%20%E2%80%9CSystem.Net.Sockets.SocketException%3A%20An%20existing%20connection%20was%20forcibly%20closed%20by%20the%20remote%20host%E2%80%9D.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2273611%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%20Support%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Co-Authors
Version history
Last update:
‎May 12 2021 10:37 AM
Updated by: