You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generally I work with more than one KeyPair in keystores, and for that it would be a good additional benefit to be able to select a KeyPair by its alias name in the #secure call (otherwise just the first valid KeyPair would selected from the given keystore).
The SslStores class + the #secure method in the Spark class could be improved concerning that.
AFAIK the JVM itself does not support this in the corresponding VM parameters (java.net.ssl. ...), so it's up to the application to handle KeyStores with multiple KeyPairs.
For example Jetty supports such an alias by a Property "certAlias" in its org.eclipse.jetty.util.ssl.SslContextFactory.
Other products use other name (certAlias, keyAlias, javax.net.ssl.keyStoreAlias) or rely on the first certificate in the KeyStore.
If this is acceptable for you, I could provide a pull request for an appropriate solution.
If not we can discuss this in detail.
The text was updated successfully, but these errors were encountered:
rozhko
added a commit
to rozhko/spark
that referenced
this issue
Jan 28, 2018
Generally I work with more than one KeyPair in keystores, and for that it would be a good additional benefit to be able to select a KeyPair by its alias name in the #secure call (otherwise just the first valid KeyPair would selected from the given keystore).
The SslStores class + the #secure method in the Spark class could be improved concerning that.
AFAIK the JVM itself does not support this in the corresponding VM parameters (java.net.ssl. ...), so it's up to the application to handle KeyStores with multiple KeyPairs.
If this is acceptable for you, I could provide a pull request for an appropriate solution.
If not we can discuss this in detail.
The text was updated successfully, but these errors were encountered: