In our PG implementation, for every connection request the device sends to PG, PG initiates a full handshake and sends a certificate to device every time. I need help, to understand how we can enable TLS 1.2 Connection resumption support in Azure Protocol Gateway.
The benefits that we are looking for are reduced time spent for the TLS handshake, reduced bandwidth usage at device end, reduced resource usage on the server.
Does this requirement needs changes in PG codebase or does it just entails setting up the Application Server that hosts the PG code base, for storing the TLS session state.
hi,
In our PG implementation, for every connection request the device sends to PG, PG initiates a full handshake and sends a certificate to device every time. I need help, to understand how we can enable TLS 1.2 Connection resumption support in Azure Protocol Gateway.
The benefits that we are looking for are reduced time spent for the TLS handshake, reduced bandwidth usage at device end, reduced resource usage on the server.
Does this requirement needs changes in PG codebase or does it just entails setting up the Application Server that hosts the PG code base, for storing the TLS session state.
Thanks, Vivek Bahl