base64 response on `/identity_record/{ID}`

[muknta]

curl http://3.123.154.245:11000/api/kira/gov/identity_record/1

expected something like that. Or at least "key" and "value", they are used in Miro.

{
  "record": {
    "address": "kira1abcde1234567890xyzexampleaddress",
    "date": "2025-02-12T22:00:00Z",
    "id": "record-001",
    "key": "user_handle",
    "value": "alice",
    "verifiers": [
      "kira1verifieraddress1",
      "kira1verifieraddress2",
      "kira1verifieraddress3"
    ]
  }
}

actual response:

"eyJyZWNvcmQiOnsiaWQiOiIxIiwiYWRkcmVzcyI6ImtpcmExZG02eTduZjJ6ZXkzOXg0M2pyczd5bXgybHhndHQ5ZWN1cTRoeHUiLCJrZXkiOiJtb25pa2VyIiwidmFsdWUiOiJcIkdFTkVTSVNcIiIsImRhdGUiOiIyMDI1LTExLTA1VDE0OjA0OjU4LjAxMzQxNTc4N1oiLCJ2ZXJpZmllcnMiOltdfX0="

[MrLutik]

@kobs30
The response encoded in base64.

[kobs30]

try http://3.123.154.245:11000/api/kira/gov/identity_records/1

[MrLutik]

try http://3.123.154.245:11000/api/kira/gov/identity_records/1

@muknta

[muknta]

@kobs30 you're right, it's working with the "Accept: application/json" header. I can live with that and put it into the request. But this endpoint's is inconsistent with others. Others are responding with json on "Accept: /".

@MrLutik we may lower the priority of this issue but it needs to be done in the same way as others in some future.

[MrLutik]

@MrLutik we may lower the priority of this issue but it needs to be done in the same way as others in some future.

@muknta Done.