Feature Request: Refuse connections of old clients

kasti · Post by **kasti** » Tue May 10, 2005 4:29 am

Hi,

My problem is that some users do not update their vault client and are having problems that have already been solved in recent versions.

Therefore i would like to add my vote to automatically update vault clients to the version running on the server.

But since this feature might take some time, would it be possible to refuse access of version mismatched vault clients. In other words, 3.0.7 server only allows 3.0.7 clients to connect? This should be an optional setting for the server because other users might not like this.

Thanks,
Herbert.

kasti · Post by **kasti** » Mon Jun 27, 2005 8:24 am

Hi,

Since there is no response to this, I guess it is not going to happen.

Different approach: Is there any way I can query the Vault server version through the SQL Server? We would then write a vault launcher, which first checks for correct version and then launches vault.

Thanks,
Herbert.

lbauer · Post by **lbauer** » Mon Jun 27, 2005 9:02 am

I can log a feature request for an option to refuse connections from mismatched clients.

Regarding your second post, I know it's possible to query the database for the schema version, but that may not always correspond to a particular version. I'll check with our SQL specialist and post again.

lbauer · Post by **lbauer** » Tue Jun 28, 2005 12:38 pm

A database query won't work for what you want, since you can only query for the schema version. The same schema version may be used for multiple Vault versions.

Instead, you could write something that makes a quick web service call to the GetVersionInfo() web service.

This will return the version of the server.