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 x509 authentication #959

Open
moritzschmitz-oviva opened this issue Dec 6, 2023 · 0 comments
Open

Support for x509 authentication #959

moritzschmitz-oviva opened this issue Dec 6, 2023 · 0 comments

Comments

@moritzschmitz-oviva
Copy link

moritzschmitz-oviva commented Dec 6, 2023

Problem Statement

The /admin path in our Keycloak instance is exposed to the public. Some of our admin users require access to the admin console. keycloak-config-cli is accessing Keycloak through an internal path though.

To add a layer of security, all our admin accounts use 2FA,
but this constraint blocks us from using keycloak-config-cli.

Since Keycloak supports x509 client authentication I would like to see keycloak-config-cli to support it. It would allow keycloak-config-cli to use a secure communications channel and would be a safe workaround for the 2FA requirement (in our use case).

Proposed Solution

Implement four new flags (following the flags from: https://www.keycloak.org/server/enabletls):

--key-store-file
--key-store-file-password
--trust-store-file
--trust-store-password

If they are set, use certificates to communicate with the Keycloak instance.

Looking at the implementation on Keycloak side it looks easy with Quarkus. Not so sure about the JBoss library used here.

Environment

  • Keycloak Version: [22.0.5]
  • keycloak-config-cli Version: [5.9.0]

Additional information

No response

Acceptance Criteria

  • [] as a user I want to be able to configure x509 client authentication
  • [] as a user I want to be able to provide the certificates for x509 client authentication
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant