How Groove handles authentication on a Secure Sockets Layer (SSL) proxy connection (916377)

MORE INFORMATION

Groove does not prompt for SSL credentials when you try to connect through an SSL proxy. The first time that Groove tries to connect to an SSL proxy that requires authentication, Groove tries to scrounge credentials from the Security Support Provider Interface (SSPI) interface.

If Groove cannot find credentials, it does not send any credentials. This occurs because Groove cannot determine whether authentication is required. Therefore, the first SSL proxy connection attempt fails. Groove cannot determine whether an SSL connection failed because there are insufficient credentials, or because the remote host is not responding.

If Groove is also trying to connect to the same proxy through Hypertext Transfer Protocol (HTTP), Groove prompts for authentication credentials for that connection. Then, Groove connects through HTTP. After that, when Groove tries to connect to the SSL proxy, Groove uses the cached credentials from the previous HTTP connection. Therefore, Groove should connect successfully.

Note Groove may use the same proxy for separate relay connections. In this case, the first relay connection uses HTTP. This is typically the home relay. All subsequent connections use SSL.