Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Uptime] Add validation for < 1 values in TLS expiration fields #65381

Closed
andrewvc opened this issue May 5, 2020 · 2 comments · Fixed by #65454
Closed

[Uptime] Add validation for < 1 values in TLS expiration fields #65381

andrewvc opened this issue May 5, 2020 · 2 comments · Fixed by #65454
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability test-plan test-plan-ok issue has passed test plan v7.8.0

Comments

@andrewvc
Copy link
Contributor

andrewvc commented May 5, 2020

It is currently possible to use negative values for TLS expiration in uptime. This makes no sense. We should use the form validator code to mark the form as in an error state if the values are < 1 or are non-integers.

image

@andrewvc andrewvc added bug Fixes for quality problems that affect the customer experience [zube]: Ready Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability v7.8.0 labels May 5, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/uptime (Team:uptime)

@justinkambic
Copy link
Contributor

I tested this by pasting negative values into the inputs. The page didn't allow me to do it:

image

image

I also verified the API disallowed these values:

image

image

This also makes me think we should have an API test verifying we get 400 errors for input like this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability test-plan test-plan-ok issue has passed test plan v7.8.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants