public-private keys from utility url not working

[answerquest]

Hi, we had trouble with the keys generated from https://sandbox.onest.network/encrypt_utility/generate/keys

Since we're no longer using them, should be safe to share, here are the initial public-private key pairs generated from the url:

{
  "public_keys" : "MhhQijpPtQ5TkBAyZI+KnOm5riw+c5K4GsyjghJaa7I=",
  "private_keys" : "tFe0CxHXpK4P1i3+k90wib5ULzmxLTjeXP3PiUC4ncI=",

Our on_search callback api wasn't accepted by bpp-client service, in the logs it said there was an invalid length of private key. I'm not able to retrieve those exact logs right now.

After that I ran npm run generate-keys in the protocol server repo. Sharing a fresh pair that I'm not using:

$ npm run generate-keys

> protocol-server_v2@1.0.0 generate-keys
> node scripts/generate-keys.js

Generating Key Pairs...

Key Pairs Generated

Your Public Key : 
 Jy9HFwue9aJvI15uOwx0ouUI4uucJBVVyVQYqXqhqwg= 

Your Private Key : 
 lxAjr7Vjikt+fo3bmi1hnOpeEB1m02kE3o01qkHNxgAnL0cXC571om8jXm47DHSi5Qji65wkFVXJVBipeqGrCA== 

I can see that the private key generated here is of longer length than the one generated by the utility url.

and used the new public-private key pair (not the same as the ones above) in our default-bpp-client.yml and default-bpp-network.yml (replacing PUBLIC_KEY PRIVATE_KEY placeholders respectivey), and re-built and re-deployed protocol server,
and then replaced the public key in our network participant on https://sandbox.onest.network/

And now it was successful.