Insecure connection prohibition
View Patent ↗A server system may be configured to receive a request for a connection from a client application. The server system may also be configured to determine if the client application is permitted to connect with the server. The connection with the client application may be prohibited if the server determines that the client application is not permitted to connect with the server. A secure connection with the client application may be permitted if the server determines that the client application is permitted to connect with the server. The secure connection may be established with the security protocol settings specified by a process on the server or shared security protocol settings specified by on a server system-wide basis.
1. A method, comprising:
receiving, by a server, a request for a connection from a client application, wherein the server hosts a plurality of processes;
determining, by the server, whether to prohibit or permit the connection with the client application based on whether or not the client application can use a secure connection;
determining, by the server, if connection security protocol settings are specified by one process on the server or if connection security protocol settings are specified on a system-wide basis on the server;
prohibiting, by the server, the connection with the client application if the server determines that the client application cannot use a secure connection; and
permitting, by the server, a secure connection with the client application if the server determines that the client application can use a secure connection, wherein the permitted secure connection is established with one of:
the one process on the server, if the connection security protocol settings are specified by the one process on the server; and
the server on the system-wide basis, if the connection security protocol settings are specified on the system-wide basis of the server.
2. The method of claim 1 , further comprising:
permitting, by the server, an insecure connection with the client application if the server determines that the client application is permitted to connect with the server and that the client application is allowed to have an insecure connection with the server.
3. The method of claim 2 , further comprising transferring data to the client application through one of:
the permitted secure connection; and
the permitted insecure connection.
4. The method of claim 2 , in which the connection security protocol comprises a secure socket layer/transport layer security (SSL/TLS) protocol.
5. The method of claim 2 , in which:
the connection security protocol settings used to establish the secure connection are indicated by an SSL/TLS handshake between the client application and the server, and
different security protocol settings are used to establish secure connections between the server and different client applications.
6. The method of claim 1 , further comprising:
creating a certificate; and
sending the certificate to a client.
7. The method of claim 6 , in which determining if the client application is permitted to connect with the server comprises:
requesting the certificate from the client application;
receiving the certificate from the client application; and
processing the certificate to validate or invalidate the client application.
8. A computer program product, comprising:
a non-transitory computer readable medium comprising code to perform the steps of:
receiving a request for a connection from a client application, wherein the server hosts a plurality of processes;
determining whether to prohibit or permit the connection with the client application based on whether or not the client application can use a secure connection;
determining if connection security protocol settings are specified by one process on the server or if connection security protocol settings are specified on a system-wide basis on the server;
prohibiting the connection with the client application if the client application cannot use a secure connection; and
permitting a secure connection with the client application if the client application can use a secure connection, wherein the permitted secure connection is established with one of:
the one process on the server, if the connection security protocol settings are specified by the one process on the server; and
the server on the system-wide basis, if the connection security protocol settings are specified on the system-wide basis of the server.
9. The computer program product of claim 8 , in which the medium further comprises code to perform the steps of:
permitting an insecure connection with the client application if the server determines that the client application is permitted to connect with the server and that the client application is allowed to have an insecure connection with the server.
10. The computer program product of claim 9 , in which the medium further comprises code to perform the step of transferring data to the client application through one of:
the permitted secure connection; and
the permitted insecure connection.
11. The computer program product of claim 9 , in which the connection security protocol comprises a secure socket layer/transport layer security (SSL/TLS) protocol.
12. The computer program product of claim 9 , in which:
the connection security protocol settings used to establish the secure connection are indicated by an SSL/TLS handshake between the client application and the server, and
different security protocol settings are used to establish secure connections between the server and different client applications.
13. The computer program product of claim 8 , in which the medium further comprises code to perform the steps of:
creating a certificate; and
sending the certificate to a client.
14. The computer program product of claim 13 , in which determining if the client application is permitted to connect with the server comprises:
requesting the certificate from the client application;
receiving the certificate from the client application; and
processing the certificate to validate or invalidate the client application.
15. An apparatus, comprising:
a memory; and
a processor coupled to the memory, the processor configured to execute the steps of:
receiving a request for a connection from a client application, wherein the server hosts a plurality of processes;
determining whether to prohibit or permit the connection with the client application based on whether or not the client application can use a secure connection;
determining, by the server, if connection security protocol settings are specified by one process on the server or if connection security protocol settings are specified on a system-wide basis on the server;
prohibiting the connection with the client application if the client application cannot use a secure connection;
permitting a secure connection with the client application if the client application can use a secure connection, wherein the permitted secure connection is established with one of:
the one process on the server, if the connection security protocol settings are specified by the one process on the server; and
the server on the system-wide basis, if the connection security protocol settings are specified on the system-wide basis of the server.
16. The apparatus of claim 15 , in which the processor is further configured to perform the steps of:
permitting an insecure connection with the client application if the server determines that the client application is permitted to connect with the server and that the client application is allowed to have an insecure connection with the server.
17. The apparatus of claim 16 , in which the processor is further configured to perform the step of transferring data to the client application through one of:
the permitted secure connection; and
the permitted insecure connection.
18. The apparatus of claim 16 , in which the connection security protocol comprises a secure socket layer/transport layer security (SSL/TLS) protocol.
19. The apparatus of claim 15 , in which:
the connection security protocol settings used to establish the secure connection are indicated by an SSL/TLS handshake between the client application and the server; and
different security protocol settings are used to establish secure connections between the server and different client applications.
20. The apparatus of claim 15 , in which the processor is further configured to perform the steps of:
creating a certificate; and
sending the certificate to a client.
21. The apparatus of claim 20 , in which determining if the client application is permitted to connect with the server comprises:
requesting the certificate from the client application;
receiving the certificate from the client application; and
processing the certificate to validate or invalidate the client application.