Affinity suite needs to support the OS proxy settings better NTLM/Kerberos/Windows SSPI/SSO

[Juniper Skunktaur]

Affinity suite needs to support the OS proxy settings better, especially when they require NTLM, Kerberos, Windows SSPI or SSO authentication credentials

In my corporate job with a network proxy we can't bypass, it just fails to accept my Serif login or download any resources. I can tether to my phone to make it work, but I really shouldn't have to.

I'd normally tell an app behaving like this to use the proxy, giving it a setting like username:password@x.x.x.x:8080 or tell it to use my installation of px-proxy (which works with apps that can take a proxy but can't use NTLM credentials) but Affinity Suite doesn't have such an option anywhere.

Nor should it - it should be using the right OS APIs that use the configured proxy and authentication for network requests.

I'm on Windows 10.

Edited February 1, 2023 by Juniper Skunktaur
clarity

[Lee D]

@Juniper Skunktaur Thanks for your feedback, I've passed it on to our Networking team to see if it's something that can improved for the future.

*UPDATE*

We do use the Windows OS proxy settings in Internet Settings, these are passed through for all web and API requests. If you can expand some more on your setup including is is and isn't working as we may need to add some additional options for proxies that haven't been configured in a particular way.

[Leigh]

@Juniper Skunktaur Can you try our recent 2.2 update to see if your issue is improved? Our developers have made some changes to the way our apps process proxy credentials. 👂