Internal end-point for ejpd request processing.

[fisx]

Attempt at streamlining the internal process at wire.com described here.

We are legally required to sometimes provide user information to law enforcement. This change introduces an internal end-point to compile the minimum required information into a json blob.

Security: to access the internal end-point, you need the same access privileges that also give you direct access to the database. So the information we provide here does not get any more accessible. On the other hand, direct database access is error prone and make result in revealing information on the wrong user due to cut&paste errors. This end-point mitigates this risk to a large extent.

[fisx]

POD LOGS: test-kwtrsypknule-wire-server-brig-integration

Parse failed: AesonException "Error in $: parsing Main.Config(Config) failed, key \"gundeck\" not found"

Falling back to environment variables

brig-integration: user error (failed to parse integration.yaml file)


Error: unable to get pod logs for test-kwtrsypknule-wire-server-cargohold-integration: pods "test-kwtrsypknule-wire-server-cargohold-integration" not found

make: *** [Makefile:262: kube-integration-test] Error 1

[fisx]

thanks @smatting: 3b8dfeb

[fisx]

    ejpd requests:                                                              FAIL
      Exception: ConnectionError (HttpExceptionRequest Request {
        host                 = "0.0.0.0"
        port                 = 8080
        secure               = False
        requestHeaders       = [("Accept","application/json;charset=utf-8,application/json"),("Content-Type","application/json;charset=utf-8")]
        path                 = "/i/ejpd-request"
        queryString          = ""
        method               = "POST"
        proxy                = Nothing
        rawBody              = False
        redirectCount        = 10
        responseTimeout      = ResponseTimeoutDefault
        requestVersion       = HTTP/1.1
      }
       (ConnectionFailure Network.Socket.connect: <socket: 46>: does not exist (Connection refused)))

Do we have to apply the change in 3b8dfeb manually? But then why did the error change?

[fisx]

The host looks suspicious, I'm pretty sure 0.0.0.0 is not gundeck's true IP :). Do I have to update something in the DNS that the brig-integration pod can see?

[fisx]

thanks @akshaymankar ! ef69c83