OAS

Thanks. I known this miss in ICS that's why I share it. SSO functionnality should be more used but I saw more cases where there is a dialog box or storage for user/PW (I do it myself when I set a windows service wich have to go throught proxy server). I hope it would pleased to dev because I think SSO is a good practice. Olivier

Hello I forgot release part so I propose you to add in OverbyteIcsHttpProt.pas, line ~1445 destructor THttpCli.Destroy; begin ..... {$IFDEF USE_NTLM_AUTH} FreeAndNil(FAuthNtlmSession); // V8.61 {$ENDIF} inherited Destroy; end;

How can I help you ?

When using ICS with proxy, you have to write user / password at each application start or store them in text file or configuration files or code (it's bad) for proxy. ICS provide fields proxyUserName and ProxyPassword for proxies. But proxies are not only usage for SSO, it's usefull for Server and Client validation on Windows wolrd (and others if you use Kerberos and other validation sytem) : Client use his credentials in place of user/password and serverdon't have to know (store) those informations, just ask to a service to validate client credentials. If you use Windows on domain, you have to use your session informations to connect wich is called Single Sign On (SSO). You are indentified once at startup and use Domain Controler to provide your identity. Windows protocol NTML is implemented for basics, can manage proxy authentification but have'nt NTLM complete implementation. In "OverbyteIcsHttpSrv" is implemented Server side to validate Domain validation but not Client side. I propose to add functionnality for Client SSO using NTLMSession yet declared with some modifications 8.61.zip