License checked assumes license UIDs are hex encoded #11640
Comments
|
FYI @ph @urso @monicasarbu. |
|
@tsg does that mean the test cluster in question don't have a valid license? |
ph
added a commit
to ph/beats
that referenced
this issue
Apr 4, 2019
There are some case where the license UUID is a valid license but not a valid UUID. Fixes: elastic#11640
ph
added a commit
to ph/beats
that referenced
this issue
Apr 4, 2019
…its system. (elastic#11649) - Relax validation of the X-Pack license UID value. - Fix a parsing error with the X-Pack license check on 32-bit system. Fixes: elastic#11640 Fixes: elastic#11650 (cherry picked from commit 4b7823b)
ph
added a commit
to ph/beats
that referenced
this issue
Apr 4, 2019
…its system. (elastic#11649) - Relax validation of the X-Pack license UID value. - Fix a parsing error with the X-Pack license check on 32-bit system. Fixes: elastic#11640 Fixes: elastic#11650 (cherry picked from commit 4b7823b)
ph
added a commit
that referenced
this issue
Apr 4, 2019
…ense UUID and check on 32 bits system. (#11657) * Fixes license check issue with invalid license UUID and check on 32 bits system. (#11649) - Relax validation of the X-Pack license UID value. - Fix a parsing error with the X-Pack license check on 32-bit system. Fixes: #11640 Fixes: #11650 (cherry picked from commit 4b7823b)
|
Would it be possible to use a hex UUID for the platinum license? There are multiple places that check the validity of the license code, so it might be safer to always adhere to a proper hex UUID - e.g. map tile server checks it, and the tile license checker relies on it too. There could be other places that I am not aware of that could also cause issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running Beats master or 6.7.0 against one of our test clusters, we got an error like this one:
We've tracked it down to the fact that the
license.uidin our development license contains atcharacter, so it's not valid hex. From what I understand, real customer licenses don't have these issue, and should only be hex, but it's probably better to just treat it as a string, to avoid such issues in the future.The text was updated successfully, but these errors were encountered: