Kibana decode base64 of heberw string into gibberish

napoxx1 · September 26, 2017, 12:47pm

Hey all,

I'm using Kibana 5.2.2 and ES 5.2.0
In one of our projects we need to insert XMLs into the Elastic search.
We are using JSON rest requests to insert the XML into the Elastic search.

Since the XML sometime have characters that break the JSON format, we decided to encode the XML with base64 - and then use the Kibana Decode base64 option to decode it for users to see in the discover tab.

The problem is with Hebrew characters, Kibana decoding from base64 converts them into gibberish..
I can only guess it is somehow related to the encoding used by Kibana when decoding the Base64.

When I tried decoding the base64 online (https://www.base64decode.org) everything was decoded correctly and the Hebrew characters were shown.

Could it be that Kibana does not use UTF-8 when decoding ?

Heres an example string containing Heberw chars - encoded with base64:
15DXmdeW16nXlNeVINeY16fXodeYINeR16LXkdeo15nXqg==

Please help

jbudz · September 26, 2017, 8:43pm

Unfortunately it looks like you're right - it only supports decoding ascii strings. In 6.0+ this is fixed and will use utf-8.

5.2 won't be getting anymore bug fixes, so in the meantime if you need to get this working. replacing

github.com

elastic/kibana/blob/5.2/src/ui/public/stringify/types/string.js#L54


_String.sampleInputs = [
  'A Quick Brown Fox.',
  'STAY CALM!',
  'com.organizations.project.ClassName',
  'hostname.net',
  'SGVsbG8gd29ybGQ='
];


_String.prototype._base64Decode = function (val) {
  try {
    return window.atob(val);
  } catch (e) {
    return _.asPrettyString(val);
  }
};


_String.prototype._toTitleCase = function (val) {
  return val.replace(/\w\S*/g, txt => { return txt.charAt(0).toUpperCase() + txt.substr(1).toLowerCase(); });
};


_String.prototype._convert = function (val) {

with return decodeURIComponent(escape(window.atob(str))) should fix things

napoxx1 · September 27, 2017, 11:05am

Hey jbudz,

Thanks for the fast help

unfortunately , the problem still persists

Is there anything else I can try ? (before upgrading to 6.0)

thanks

system · October 25, 2017, 11:05am

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.