Configure a secure MID Web Server extension
Configure a TLS listener for extra security and encryption of data transferred to and from the MID Web Server extension. Access both a private key and a certificate (or certificate chain) from a Java keystore to use during the TLS handshake where the MID Web Server and the client acknowledge each other.
Before you begin
Role required: agent_client_collector_admin
Procedure
Navigate to MID Server > Extensions > MID Web Server.
Select New.
In the Authentication Type field, select an authentication type to be used.
- Keybased – See Configure key-based MID Web Server authentication
- Basic – Standard username/password authentication
- API key – See Configure MID Web Server API key authentication
- mTLS – See MID Web Server and agent mTLS Authentication
- Select either the MID unified keystore or the web server keystore.
The MID Web Server unified keystore is the most efficient option. If you want to enable backward compatibility and the ability to store keypairs in an additional keystore, use the Web server keystore (which allows you to use the MID unified keystore as well).
| Option | Description |
|---|---|
| MID unified keystore |
For more information, see the Install custom certificates in the MID Server unified key store section in MID Server unified key store. Important: Leaving the Keystore Certificate Alias field empty causes connecting clients to skip certificate verification. Instead, the MID Server uses its own self-signed certificate. |
| Web server keystore |
|
Related topics