Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

keyAlias is not yet supported #1238

Closed
Thadir opened this issue Aug 22, 2024 · 4 comments · Fixed by #1241
Closed

keyAlias is not yet supported #1238

Thadir opened this issue Aug 22, 2024 · 4 comments · Fixed by #1241
Assignees

Comments

@Thadir
Copy link

Thadir commented Aug 22, 2024

Goodday,

I am trying to set up a custom proxy and based on the documetation found here:

I setup my sericeProxy as follows:

<serviceProxy name="SslClientForwardService">
   <path>SslClientForwardService</path>
   <ssl>
      <keystore keyAlias="SslClientForwardService" />
  </ssl>
</serviceProxy>

But when I run this I get the following stacktrace:
15:44:21,515 DEBUG 1 main Router:141 - loading spring config: file:/app/conf/proxies.xml
15:44:22,634 DEBUG 1 main RelocatingInterceptor:125 - protocol property set for WSDL Rewriting Interceptor:https
15:44:22,639 DEBUG 1 main RelocatingInterceptor:125 - protocol property set for WSDL Rewriting Interceptor:https
org.springframework.context.ApplicationContextException: Failed to start bean 'router'
at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:291)
at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:471)
at java.base/java.lang.Iterable.forEach(Unknown Source)
at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:260)
at org.springframework.context.support.DefaultLifecycleProcessor.start(DefaultLifecycleProcessor.java:174)
at org.springframework.context.support.AbstractApplicationContext.start(AbstractApplicationContext.java:1521)
at com.predic8.membrane.core.Router.init(Router.java:147)
at com.predic8.membrane.core.RouterCLI.main(RouterCLI.java:39)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at com.predic8.membrane.core.Starter.main(Starter.java:47)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.security.InvalidParameterException: keyAlias is not yet supported.
at com.predic8.membrane.core.Router.start(Router.java:316)
at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:288)
... 12 more
Caused by: java.lang.RuntimeException: java.security.InvalidParameterException: keyAlias is not yet supported.
at com.predic8.membrane.core.transport.ssl.StaticSSLContext.(StaticSSLContext.java:198)
at com.predic8.membrane.core.rules.AbstractServiceProxy.init(AbstractServiceProxy.java:128)
at com.predic8.membrane.core.rules.ServiceProxy.init(ServiceProxy.java:38)
at com.predic8.membrane.core.rules.AbstractProxy.init(AbstractProxy.java:163)
at com.predic8.membrane.core.Router.initRemainingRules(Router.java:269)
at com.predic8.membrane.core.Router.init(Router.java:263)
at com.predic8.membrane.core.Router.start(Router.java:288)
... 13 more
Caused by: java.security.InvalidParameterException: keyAlias is not yet supported.
at com.predic8.membrane.core.transport.ssl.StaticSSLContext.(StaticSSLContext.java:89)
... 19 more

Witch is a bit counter productive as I see it in the doc available without the info that its not yet supported.

@rrayst
Copy link
Contributor

rrayst commented Aug 23, 2024

Hi Thadir,

thanks for reporting this. You are absolutely right and we will look into that.

In the meantime, please use key stores with only one key entry and don't specify the keyAlias in Membrane's proxies.xml.

Thanks
Tobias

@Thadir
Copy link
Author

Thadir commented Aug 26, 2024

Yeah this is the way it used to work.

But it makes it a bit clutterd it would be nice to just have one keystore to monitor. I sugest updating the documetation to represent this. And of course the major questino when will this feature be supported.

@predic8
Copy link
Member

predic8 commented Aug 26, 2024

@Thadir we are working on the feature and we'll ship it probably with the next minor version.

@t-burch
Copy link
Collaborator

t-burch commented Aug 29, 2024

@Thadir the feature is ready and will be merged soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants