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

Expose "is TLS enabled" flag for Kibana HTTP Server #40336

Merged
merged 5 commits into from
Jul 9, 2019

Conversation

mshustov
Copy link
Contributor

@mshustov mshustov commented Jul 4, 2019

Summary

Expose boolean flag indicating if TLS enabled for Kibana HTTP server.
The frist commit introduces flag.
The second one restructures tests to move all setup contract related tests under one section.

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

For maintainers

@mshustov mshustov added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:New Platform release_note:skip Skip the PR/issue when compiling release notes v7.4.0 labels Jul 4, 2019
@mshustov mshustov requested a review from a team as a code owner July 4, 2019 07:30
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Member

@azasypkin azasypkin left a comment

Choose a reason for hiding this comment

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

LGTM from the security perspective and does what we need in #39446

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Contributor

@joshdover joshdover left a comment

Choose a reason for hiding this comment

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

LGTM, just a small naming nit

@@ -75,6 +75,7 @@ export interface HttpServerSetup {
isAuthenticated: AuthStateStorage['isAuthenticated'];
getAuthHeaders: AuthHeadersStorage['get'];
};
isTLSEnabled: boolean;
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this should be capitalized isTlsEnabled to be consistent with HttpServer and SslConfig

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@mshustov mshustov merged commit ff5b7a8 into elastic:master Jul 9, 2019
kibana-core [DEPRECATED] automation moved this from Code review to Needs Backport Jul 9, 2019
@mshustov mshustov deleted the expose-http-isTLSEnabled branch July 9, 2019 17:18
mshustov added a commit to mshustov/kibana that referenced this pull request Jul 9, 2019
* expose it TLS enabled on Http server

* setup contract is under one section in tests

* regenerate docs

* isTLSEnabled --> isTlsEnabled
mshustov added a commit that referenced this pull request Jul 9, 2019
* expose it TLS enabled on Http server

* setup contract is under one section in tests

* regenerate docs

* isTLSEnabled --> isTlsEnabled
toddself pushed a commit to toddself/kibana that referenced this pull request Jul 9, 2019
* expose it TLS enabled on Http server

* setup contract is under one section in tests

* regenerate docs

* isTLSEnabled --> isTlsEnabled
@mshustov mshustov moved this from Needs Backport to Done (this week) in kibana-core [DEPRECATED] Jul 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backported Feature:New Platform release_note:skip Skip the PR/issue when compiling release notes Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v7.4.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants