gchq / gchq/stroom-proxy

custom truststore with stroom-proxy docker image

Open
#29 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
6
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Hi,
I am having some issues using the gchq/stroom-proxy:latest build.
I can curl my stroom with the custom truststore but cannot work out where i need to place the truststore or how to configure the stroom.properties file:
```
javaOpts="-Djavax.net.ssl.trustStore=/etc/ca-certificates"

```
error i get from the proxy log:
```
stroom-proxy-gchq | 2020-05-29T00:14:35.765Z ERROR [http-bio-9080-exec-1] remoteclient.RemoteFeedServiceCacheable (RemoteFeedServiceCacheable.java:40) - handleHeader() - Unable to check remote feed service (request TEST-FEED-V1_0).... will assume OK (response Receive) - Cannot access Hessian remote service at [https://stroom/stroom/remoting/remotefeedservice.rpc]; nested exception is javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
stroom-proxy-gchq | 2020-05-29T00:14:35.792Z INFO [http-bio-9080-exec-1] datafeed.DataFeedRequestHandler$1 (DataFeedRequestHandler.java:102) - "doPost() - Took 214ms to process (concurrentRequestCount=1) 200","GUID=29b36365-06c6-40ff-9fce-2c92300b30d3","ReceivedTime=2020-05-29T00:14:35.580Z","RemoteAddress=172.18.200.1","RemoteHost=172.18.200.1","accept=*/*","accept-encoding=gzip, deflate, br","connection=keep-alive","content-length=11","content-type=text/plain","environment=EXAMPLE_ENVIRONMENT","feed=TEST-FEED-V1_0","host=172.18.200.6:9080","postman-token=69f40154-0a12-4255-8ec9-4c85631ba88a","system=EXAMPLE_SYSTEM","user-agent=PostmanRuntime/7.25.0"
```

I hope this is the right place for this.

Cheers

duncan

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the gchq/stroom-proxy:latest Docker image and the stroom.properties javaOpts setting described in the issue. Check how the custom truststore is placed and passed to Java, using the proxy log's trustAnchors error as the failure signal. Done means the proxy can access the remote Stroom Hessian service over HTTPS without that error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, java
Domain
devops, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.