KSQLDB fails to start if ssl.keystore.type=pkcs12 instead of ssl.keystore.type=PKCS12
#6,064 建立於 2020年8月20日
描述
Describe the bug A clear and concise description of what the bug is.
KSQLDB fails to start if ssl.keystore.type=pkcs12 instead of ssl.keystore.type=PKCS12
To Reproduce Steps to reproduce the behavior, include:
- The version of KSQL.
- Sample source data.
- Any SQL statements you ran
Latest version of KSQLDB with Java 11 and FIPS support enabled.
Expected behavior A clear and concise description of what you expected to happen.
KSQLDB should start even if ssl.keystore.type=pkcs12, case sensitivity should be irrelevant for this property.
Actual behaviour A clear and concise description of what actually happens, including:
- CLI output
- Error messages
- KSQL logs
Essentially if you have ssl.keystore.type=pkcs12 it fails with the following stack:
[2020-08-20 11:42:09,539] ERROR Failed to start KSQL (io.confluent.ksql.rest.server.KsqlServerMain:66) org.apache.kafka.common.config.ConfigException: Invalid value pkcs12 for configuration ssl.keystore.type: String must be one of: JKS, PKCS12 at org.apache.kafka.common.config.ConfigDef$ValidString.ensureValid(ConfigDef.java:970) at org.apache.kafka.common.config.ConfigDef.parseValue(ConfigDef.java:512) at org.apache.kafka.common.config.ConfigDef.parse(ConfigDef.java:496) at org.apache.kafka.common.config.AbstractConfig.(AbstractConfig.java:108) at org.apache.kafka.common.config.AbstractConfig.(AbstractConfig.java:129) at io.confluent.ksql.rest.server.KsqlRestConfig.(KsqlRestConfig.java:571) at io.confluent.ksql.rest.server.KsqlServerMain.createExecutable(KsqlServerMain.java:116) at io.confluent.ksql.rest.server.KsqlServerMain.main(KsqlServerMain.java:59)
Additional context Add any other context about the problem here.
Other components in the Kafka ecosystem which use this same property do not have this case sensitivity issue. It appears to be related to enabling FIPS.