Spaces Color Picker - Error with valid hex values

[jonsoini]

Kibana version:
7.3.0

Elasticsearch version:
7.3.0

Server OS version:
(N/A - Elastic Cloud)

Browser version:
Chrome 76.0.3809.100 and Safari 12.1.2 (14607.3.9)

Browser OS version:
Mojave 10.14.6 (18G87)

Original install method (e.g. download page, yum, from source, etc.):
Elastic Cloud install

Describe the bug:
I receive an error message when creating or editing a Space in Kibana and when a custom color is chosen via the color picker.

UI error:
Error saving space:

(I'm able to create or edit spaces when no color value is chosen)

Steps to reproduce:

1. Management > Spaces
2. Create a new space, assign a custom color, like #e20074
3. Receive error message

Expected behavior:
Should be able to create or edit a space with a custom color.

Errors in browser console (if relevant):

{statusCode: 400, error: "Bad Request",…}
error: "Bad Request"
message: "child "color" fails because ["color" with value "#E20074" fails to match the 6 digit hex color, starting with a # pattern]"
statusCode: 400
validation: {source: "payload", keys: ["color"]}
keys: ["color"]
source: "payload"

Any additional context:
An elastic solution architect confirmed the bug with their cloud instance in addition to mine.

[hemantmalik]

++
I get the same when tried on my cloud instance. I don't get this on a local install.

[elasticmachine]

Pinging @elastic/kibana-security

[legrego]

Thanks for the report @jonsoini.

It looks like the Spaces API doesn't allow for upper-case characters to be used, but the color picker is trying to specify just that.

I've opened #43470 to address this.

[legrego]

v8.0: b8303e4

v7.4: 633b58e

v7.3.2: b3ba5e6

[jonsoini]

23 hours?! I can't get some folks to answer a Slack message that fast. You folks are awesome!

[rashmivkulkarni]

Tried on 7.3.2 cloud instance - works fine on 7.3.2, 7.4.0