Skip to content

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

Merged
mshustov merged 5 commits intoelastic:masterfrom
mshustov:expose-http-isTLSEnabled
Jul 9, 2019
Merged

Expose "is TLS enabled" flag for Kibana HTTP Server#40336
mshustov merged 5 commits intoelastic:masterfrom
mshustov:expose-http-isTLSEnabled

Conversation

@mshustov
Copy link
Copy Markdown
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 Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t// 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
Copy Markdown
Contributor

Pinging @elastic/kibana-platform

@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

Copy link
Copy Markdown
Contributor

@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
Copy Markdown
Contributor

💚 Build Succeeded

Copy link
Copy Markdown
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

isAuthenticated: AuthStateStorage['isAuthenticated'];
getAuthHeaders: AuthHeadersStorage['get'];
};
isTLSEnabled: boolean;
Copy link
Copy Markdown
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
Copy Markdown
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
Copy Markdown
Contributor

💚 Build Succeeded

@mshustov mshustov merged commit ff5b7a8 into elastic:master 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
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 Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t// v7.4.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants