-
Notifications
You must be signed in to change notification settings - Fork 269
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
Securing registry with Keycloak with untrusted certificate #1693
Comments
Hi, Quarkus properties will not work since this is something that is happening in a custom controller. You need to import the certificate into the keystore. If you're running in docker, this is something you can done with something like this:
|
If you're using the application without the UI yes, you can customize the roles. If you're using the UI then no, roles are fixed in the UI. We know this is a problem and is something that will be changed in future versions. |
Since the certs are provided by the runtime-platform and not at buildtime I added our tuststore.pem to Using |
The bug where the roles are not customizable is fixed and will be available in a 2.1.x release. Maybe we need to backport the fix and release |
As for the root problem, I would have expected the We would probably need to reproduce this locally to dig into it any further, wdyt @carlesarnal ? |
thats good news. is there a release date for the 2.1.x release? For us the renaming of roles is required. Depending on the release date a backport to i'll recheck the certificate issue as i would also expect the |
I was able to sort out the certificate issue. root cause was that I directly added the pem to the cacerts which did not add it in a correct way. using a backport of the role-name changing feature to 2.0.2 would still be highly appreciated. |
Release date for 2.1.0 is "soon". :) I'm out on PTO for 2 weeks starting next week - we probably won't get a release done before that, and not sure if we would do one while I'm out. Maybe. |
Hi there
I'm currently using
apicurio/apicurio-registry-sql:2.0.1.Final
and try to secure the registry with keycloak.As our keycloak does not have a trusted certificate we are running in the following stacktrace:
Used Environment Variables:
I tried the following without any luck:
quarkus.oidc.tls.verification=none
(mountpath: /deployments/config/application.properties)quarkus.http.ssl.certificate.trust-store-file=/deployments/tls/ca/truststore.jks
-Djavax.net.ssl.trustStore
Has anyone managed to get a running setup with an untrusted keycloak certificate?
Another question related to securing the registry with keycloak. Is it possible to change the role names by overriding
registry.auth.roles.admin=some-other-admin-role
?The text was updated successfully, but these errors were encountered: