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

Be more strict when handling the access token #9624

Merged
merged 5 commits into from
Dec 18, 2018

Conversation

ph
Copy link
Contributor

@ph ph commented Dec 18, 2018

Add validations for the Kibana response with the access token,
and enforce that the access token is not empty when unpacking the
configuration. Since the access token in the keystore could be edited.

Fixes: #9621

Add validations for the Kibana response with the access token,
and enforce that the access token is not empty when unpacking the
configuration. Since the access token in the keystore could be edited.

Fixes: elastic#9621
@ph ph added in progress Pull request is currently in progress. Management labels Dec 18, 2018
@ph ph requested a review from a team as a code owner December 18, 2018 15:35
@ph ph added review needs_backport PR is waiting to be backported to other branches. and removed in progress Pull request is currently in progress. labels Dec 18, 2018
@ph ph requested a review from urso December 18, 2018 15:38
@@ -66,6 +67,8 @@ const ManagedConfigTemplate = `
#xpack.monitoring.elasticsearch:
`

var errEmptyAccessToken = errors.New("access_token is empty, you must reenroll your beats")
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/beats/Beat/

@ph
Copy link
Contributor Author

ph commented Dec 18, 2018

updated with the changes.

@ph ph merged commit 8dd740f into elastic:master Dec 18, 2018
ph added a commit to ph/beats that referenced this pull request Dec 18, 2018
Add validations for the Kibana response with the access token,
and enforce that the access token is not empty when unpacking the
configuration. Since the access token in the keystore could be edited.

Fixes: elastic#9621
(cherry picked from commit 8dd740f)
@ph ph added v6.6.0 and removed needs_backport PR is waiting to be backported to other branches. labels Dec 18, 2018
ph added a commit that referenced this pull request Dec 19, 2018
…en (#9643)

Cherry-pick of PR #9624 to 6.x branch. Original message: 

Add validations for the Kibana response with the access token,
and enforce that the access token is not empty when unpacking the
configuration. Since the access token in the keystore could be edited.

Fixes: #9621
ph added a commit to ph/beats that referenced this pull request Dec 24, 2018
Add validations for the Kibana response with the access token,
and enforce that the access token is not empty when unpacking the
configuration. Since the access token in the keystore could be edited.

Fixes: elastic#9621
(cherry picked from commit 8dd740f)
@ph ph added the v6.5.5 label Dec 24, 2018
ph added a commit to ph/beats that referenced this pull request Dec 24, 2018
Add validations for the Kibana response with the access token,
and enforce that the access token is not empty when unpacking the
configuration. Since the access token in the keystore could be edited.

Fixes: elastic#9621
(cherry picked from commit 8dd740f)
ph added a commit that referenced this pull request Jan 8, 2019
…en (#9790)

Cherry-pick of PR #9624 to 6.5 branch. Original message: 

Add validations for the Kibana response with the access token,
and enforce that the access token is not empty when unpacking the
configuration. Since the access token in the keystore could be edited.

Fixes: #9621
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…ess token (elastic#9790)

Cherry-pick of PR elastic#9624 to 6.5 branch. Original message: 

Add validations for the Kibana response with the access token,
and enforce that the access token is not empty when unpacking the
configuration. Since the access token in the keystore could be edited.

Fixes: elastic#9621
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants