[
https://issues.apache.org/jira/browse/FLINK-25866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498493#comment-17498493
]
Fil Karnicki edited comment on FLINK-25866 at 2/28/22, 9:42 AM:
----------------------------------------------------------------
Thanks [~trohrmann] :)
//edit [I had an issue where an e2e test didn't pass, but it's now solved, so
removing the rest of this comment]
was (Author: JIRAUSER284249):
Thanks [~trohrmann] :)
Hi [~igal] I'm almost ready to make a pull request, but I'm facing an issue in
the e2e java test where the `ResourceLocator` is unable to get any resources
(which is not the case in unit statefun-flink-core tests). There's something
that I don't understand about this resource loading; is there any chance you
could have a look and let me know what you think please?
Here's my fork: [https://github.com/FilKarnicki/flink-statefun/pull/2]
and the exception:
21:13:53,669 INFO org.apache.flink.statefun.e2e.smoke.SmokeRunner
- java.lang.IllegalStateException: Resource classpath:a_client.key not found
21:13:53,669 INFO org.apache.flink.statefun.e2e.smoke.SmokeRunner
- at
org.apache.flink.statefun.flink.core.httpfn.DefaultHttpRequestReplyClientFactory.lambda$null$5(DefaultHttpRequestReplyClientFactory.java:154)
~[statefun-flink-core.jar:3.3-SNAPSHOT]
running:
org.apache.flink.statefun.e2e.smoke.java.SmokeVerificationJavaE2E
Many thanks
Fil
> Support additional TLS configuration.
> -------------------------------------
>
> Key: FLINK-25866
> URL: https://issues.apache.org/jira/browse/FLINK-25866
> Project: Flink
> Issue Type: Improvement
> Components: Stateful Functions
> Reporter: Igal Shilman
> Assignee: Fil Karnicki
> Priority: Major
>
> Currently the default HTTP client used to invoke remote functions does not
> support customising the TLS settings as part of the endpoint spec definition.
> This includes
> using self-signed certificates, and providing client side certificates for
> authentication (which is a slightly different requirement).
> This issue is about including additional TLS settings to the default endpoint
> resource definition, and supporting them in statefun-core.
> User mailing list threads:
> * [client cert auth in remote
> function|https://lists.apache.org/thread/97nw245kxqp32qglwfynhhgyhgp2pxvg]
> * [endpoint self-signed certificate
> problem|https://lists.apache.org/thread/y2m2bpwg4n71rxfont6pgky2t8m19n7w]
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
