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

Support for tls v1.3 in opensearch-dashboards #838

Closed
aggarwalShivani opened this issue Oct 4, 2021 · 4 comments · Fixed by #5133
Closed

Support for tls v1.3 in opensearch-dashboards #838

aggarwalShivani opened this issue Oct 4, 2021 · 4 comments · Fixed by #5133
Assignees
Labels
enhancement New feature or request technical debt If not paid, jeapardizes long-term success and maintainability of the repository.

Comments

@aggarwalShivani
Copy link

Description:

(link to original query)
Opensearch supports TLS v1.3 for both http and transport-layer communication.
(Ref - https://github.com/opensearch-project/OpenSearch/blob/0ba0e7cc26060f964fcbf6ee45bae53b3a9941d0/libs/ssl-config/src/main/java/org/opensearch/common/ssl/SslConfiguration.java#L69)

However, opensearch-dashboards also does not support tls 1.3 yet. (Ref -

schema.oneOf([schema.literal('TLSv1'), schema.literal('TLSv1.1'), schema.literal('TLSv1.2')]),
)

Issue: As a result, if opensearch runs with tls 1.3 enabled for http communication, opensearch-dashboard would fail to connect to opensearch and wont start.
Note - In kibana, TLS 1.3 is supported only from 7.11.0 and not available in older versions i.e. 7.10 from which opensearch-dashboards is derived.

This feature is to request support for tls 1.3.

@aggarwalShivani aggarwalShivani added the enhancement New feature or request label Oct 4, 2021
@tmarkley tmarkley added the technical debt If not paid, jeapardizes long-term success and maintainability of the repository. label May 25, 2022
@aggarwalShivani
Copy link
Author

Hi,
Can you help us with the plan for supporting TLS 1.3 on Opensearch-dashboards? There is no update from last 1yr and we're really looking forward to move to TLS 1.3.

@stephen-crawford
Copy link

@kajetan-nobel could you leave a comment so you can be assigned to this issue? Thank you :)

@kajetan-nobel
Copy link
Contributor

@scrawfor99 Sorry, I didn't see that 😅. So - I'm on it :)

@davidlago
Copy link

Ready for review now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request technical debt If not paid, jeapardizes long-term success and maintainability of the repository.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants