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

[Feature]: Keycloak TLS 1.2 support #536

Open
1 task done
pmig opened this issue Mar 7, 2024 · 0 comments
Open
1 task done

[Feature]: Keycloak TLS 1.2 support #536

pmig opened this issue Mar 7, 2024 · 0 comments

Comments

@pmig
Copy link
Member

pmig commented Mar 7, 2024

Checklist

  • I've searched for similar issues and couldn't find anything matching

Is this feature request related to a problem?

None

Problem Description

Although TLS 1.2 is already deprecated, some customers still need to maintain clients, that does only support TLS 1.2

Solution Description

We need to add an option for optionally passing TLS schemes in the CRD during start, so we can start Keycloak with an additional --https-protocols=<protocol>[,<protocol>] option.

For more information see: https://www.keycloak.org/server/enabletls

Benefits

Additional configuration options.

Potential Drawbacks

No response

Additional Information

We could also create a generic solution to allow a custom map or list of args.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant