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.

Sign up for GitHub

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

Jump to bottom

Update Schema-Registry to use latest Pravega Client for TLS 1.3 support and latest Keycloak client #209

Closed
kotlasaicharanreddy opened this issue Jul 27, 2021 · 0 comments · Fixed by #216 or #221
Closed

Update Schema-Registry to use latest Pravega Client for TLS 1.3 support and latest Keycloak client #209

kotlasaicharanreddy opened this issue Jul 27, 2021 · 0 comments · Fixed by #216 or #221

Comments

@kotlasaicharanreddy
Copy link
Contributor

kotlasaicharanreddy commented Jul 27, 2021 •
edited by sarlaccpit
Loading

Problem description
Schema-Registry doesn't' support TLS Protocol Version 1.3
Additionally, though it is not required for TLS1.3 support, the latest Keycloak client should be updated to be consistent with other components of the Pravega landscape, such as the Flink/Spark connectors.

Problem location

Suggestions for an improvement
Updating Pravega client to latest version will support TLS 1.3.
Updating Pravega Keycloak client to latest version to support Keycloak 12.
@sarlaccpit sarlaccpit changed the title Update Schema-Registry to use latest Pravega Client for TLS 1.3 support Update Schema-Registry to use latest Pravega Client for TLS 1.3 support and latest Keycloak client Jul 29, 2021
@sarlaccpit sarlaccpit mentioned this issue Jul 29, 2021
Merged
@shshashwat shshashwat mentioned this issue Aug 13, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@kotlasaicharanreddy