Versions Compared

Old Version 18

changes.mady.by.user Jakub Scholz

Saved on

compared with

New Version 19

changes.mady.by.user Jakub Scholz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Use rest.advertised.security.listener instead of rest.advertised.security.protocol

...

The rest.advertised.host.name and rest.advertised.port options will continue to be used as today to specify the connection address which should be used by other workers. In addition a new option rest.advertised.security.protocollistener will define whether other workers should connect using HTTP or HTTPS protocols. In case HTTPS is selected, the connecting worker will use the SSL configuration from the existing ssl.* options. Even in case when rest.advertised.host.name and rest.advertised.port options are not specified this field will be used to define which protocol should be advertised to other workers in combination with the appropriate hostname and port from the listener field.

...

ParameterDefault valueNote
listenersnullList of REST listeners in the format protocol://host:port,protocol2://host2:port2 where the protocol is one of HTTP and HTTPS.

rest.advertised.security.

protocol

listener

null

Configures the protocol listener used for communication between workers. Valid values are either HTTP or HTTPS.

When the listeners configuration is not defined or when it contains HTTP listener, the default value for this field will be HTTP. When the listeners option is configured and contains only HTTPS listener, the default value will be HTTPS.

ssl.client.authnoneValid values are none, requested and required. It will controls whether:
  • the connecting client is required to do SSL/TLS client authentication (required) 
  • it can decide to skip the SSL/TLS client authentication (requested) 
  • the SSL/TLS authentication will be completely disabled (none)

This is the only authentication option suggested as part of this KIP.

listeners.https.ssl.* The listeners.https. prefix can be used with any SSL configuration option mentioned below to override the default SSL configuration which is shared with the connections to Kafka broker. In case at least one option with this prefix exists, the implementation will use only SSL options with this prefix and will ignore all options without prefix. In case no option with prefix listeners.https. exists, the options without prefix will be used.

...