Trying to test the docker container v1.2 and getting HTTP 500

[tapantfspl]

Hi. I am trying to use the docker container v1.2 before integration with our TSP code modules.

I am getting HTTP 500 presently with no message.

Steps that I executed.
a. Started docker container on 8080 and browsed to swagger-ui
b. Created 2 key pairs using "/x25519/v1/generateKey" - named them KP1 and KP2
c. Used KP1's private key and KP2's public key as input to "/x25519/v1/getSharedKey"

Got HTTP 500 response with following body.

{
"timestamp": "2022-10-11T07:34:16.849+0000",
"status": 500,
"error": "Internal Server Error",
"message": "No message available",
"path": "/x25519/v1/getSharedKey"
}

Assumptions - the generated key pairs are in proper format - I am not doing any conversion / transformation etc on the keys provided.

Our use case is that we want the docker container to be hosted privately and call it from our product (which is a .NET Core based product).

Any help will be appreciated.

Thanks
Tapan Trivedi (Finacus Solutions).

[tapantfspl]

Further update:

My request json to getSharedKey was faulty. It would have been good if the setters had JsonProperty defined. It would have trapped incorrect request.

[gsasikumar]

Provide a sample we can try and see if we can address that clearly

[tapantfspl]

Hi , I have deployed the service on a linux machine now and have exposed it as APIs. Its working fine for me now. For the specific use case of docker - my deployment is on windows and with .Net dev environment. I have concluded that on Windows this particular docker container is an issue (not the container per say but docker on windows is somehow not working out). It's not a priority presently. Re Tapan

…

-- *Tapan Trivedi*

On Wed, Nov 9, 2022 at 5:58 PM Sasikumar Ganesan ***@***.***> wrote: Provide a sample we can try and see if we can address that clearly — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: External Email...Caution Could be SPAM sophospsmartbannerend Provide a sample we can try and see if we can address that clearly — Reply to this email directly, view it on GitHub <https://us-east-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL1NhaGFtYXRpL3JhaGFzeWEvZGlzY3Vzc2lvbnMvMjcjZGlzY3Vzc2lvbmNvbW1lbnQtNDA5NjYxNw==&i=NjIyODNmMzAyNDNkNjYxMjNjYTdkZDEy&t=eXJEa1p2UGM2NEU4MXhqV24wczBGUVhQOWpZN3AyYlc3ZDNBMlBUcGI0Yz0=&h=86ca0458a50a4cd095467bafa90aeb9a&s=AVNPUEhUT0NFTkNSWVBUSVb5ANN_SyiGPrcsfDsMAnynIxGUWs-MzxRaQ5795haRcA>, or unsubscribe <https://us-east-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL25vdGlmaWNhdGlvbnMvdW5zdWJzY3JpYmUtYXV0aC9BVVIyNFpBTTdFTDRORFQyR1VZNlE2RFdIT0tFUkFOQ05GU002QUFBQUFBUkNBQ1VRWQ==&i=NjIyODNmMzAyNDNkNjYxMjNjYTdkZDEy&t=VUpWVjRHQytFT1p3V3F2Wk5za3F3dWJNZGlnZHljdmtCcGhOTDJJTVd0dz0=&h=86ca0458a50a4cd095467bafa90aeb9a&s=AVNPUEhUT0NFTkNSWVBUSVb5ANN_SyiGPrcsfDsMAnynIxGUWs-MzxRaQ5795haRcA> . You are receiving this because you authored the thread.Message ID: ***@***.***>