rest-client | automated testing REST API , generating exquisite testing | REST library

1. First, you need to enable Jackson, as RESTEasy defaults to JSONB. For this you need to add this system property:

• resteasy.preferJacksonOverJsonB = true

Add system property as your preference, using -Dproperty=value command line syntax or whatever. In our case, we use WildFly configuration (e.g. standalone.xml):

Auth depends on cookies, your browser automatically sends the cookies. But when you use cURL cookies are not present, hence auth cannot authenticate. Next-Auth cookies

You have both classic RESTEasy (quarkus-resteasy-jsonb, quarkus-resteasy-mutiny) and RESTEasy Reactive (quarkus-resteasy-reactive). You need to pick one and stick to it.

For example, if you want RESTEasy Reactive, you'd remove quarkus-resteasy-mutiny (no need for extra dependency with RESTEasy Reactive), and replace quarkus-resteasy-jsonb with quarkus-resteasy-reactive-jsonb.

You RestClient method should return a JAX-RS Response object instead of the payload so you can access the header from it via getHeaders.

You are using Hibernate Search 5, which is old, with a recent version of Spring.

Hibernate Search 5, being old, depends on an old version of the Elasticsearch client JARs.

Your version of Spring depends on a newer, incompatible version of the Elasticsearch client JARs.

Two solutions:

1. Upgrade to the newer Hibernate Search 6, which will most likely depend on a version of Elasticsearch that is compatible with the one bundled with Spring. Note that just changing the version won't be enough: group IDs, artifact IDs and APIs are different. See the migration guide.

2. OR try to downgrade to an older version of the Elasticsearch client. For example, with Spring Boot:

Spring Data Elasticsearch never closes the client as it does not create it, you create it in your configuraiton.

And like the linked document states:

you should close the high-level client when you are well and truly done with it

Spring Data Elasticsearch cannot know if and when your application does not need the connection to Elasticsearch any more.

So you might keep a reference to the client and close it if you think you really don't need it. But any calls to ElasticsearchOperations or repositories will fail after that.

Actually I never heard of a problem because of wasted resources of a single instance of this class in an application, I'd say don't bother with closing it.

In your project directory, try installing rails gem install rails -v 4.1.6 and removing the version from the failing gems like (liquid_markdown, gon, etc..) then try running bundle update then bundle clean --force

I think this might be an issue because all the version of these gems are locked inside your Gemfile

In such a case, org4 will only user crypto material given to it by the network operator to connect to the network and invoke chaincode. Following does not make sense to me.

Is it possible for org4 identity to invoke transactions on org1 peers?

From my understanding, as long as you have cyrpto material to connect to HLF, and you have the right connection profile in place, the HLF client that org4 runs, would end up posting transaction to all peers, check the simulation result on the HLF client side, and then send the transaction to orderer for it to be comitted onto the peers.

So, in your case we'll have a new user created for org4 to use, and then org4 would use that crypto material to invoke the chaincodes. A transaction submitted by any org will end up getting executed by all participating org's infrastructure, so someone does not want to contribute infra, they'll just use crypto material to connect to HLF network by not addition and reuse existing chaincodes put up on peers.

The code running on your local computer is trying to connect directly to the Elasticsearch server without going through the SSH tunnel. The SSH command is opening a tunnel from your local port 9200 to the remote server. The local software trying to connect to Elasticsearch should be connecting to localhost:9200 not vpc-es-domain-20210331-abc123def.us-west-2.es.amazonaws.com/10.0.47.182:443.

The endpoint vpc-es-domain-20210331-abc123def.us-west-2.es.amazonaws.com/10.0.47.182:443 doesn't look valid anyway. It has a hostname and an IP address in there.

You mentioned in the comments:

"I actually launched my bastion host using the same SG as my ES"

However just placing two resources in the same security group does nothing unless that security group also has a rule specifically allowing traffic between the resources within it. Security groups do not have this rule by default, except for the default security group in the default VPC that is created automatically when you first create your AWS account.

So please make sure that the security group has a rule that will allow the bastion host to connect to the Elasticsearch server over port 443.