Thanks so much for tracking this down.  The fix you provided works.

Hello Richard,

I am able to reproduce the issue and I have asked our engineering staff to examine this further.  To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 274207.

I have created a private case C-00224085 for you to link this bug. You can access the provate case and see the progress f the issue from your infragistics account.

For a time being As a workaround I tried this after InitializeComponent in the constructor ,and irworks for me . May be you can try at your end too.

 InitializeComponent(); 

 const SslProtocols _Tls12 = (SslProtocols)0x00000C00;
 const SecurityProtocolType Tls12 = (SecurityProtocolType)_Tls12;
 ServicePointManager.SecurityProtocol = Tls12;

 Regarding the issue ,the next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution.

Regards,

Divya Jain

This is WPF not winforms. Here is an image of the exception.

Hello Richard,

Thank you for the update that using https request for blazor fixed the issue. For WPF may i know which exception you are getting ? May be application need to enable some kind of security constrain ,which i am not sure yet until i see the exception i can provide more information.