SAML client import cert pem file for "Encryption keys config" broken

[wilderk]

Before reporting an issue

• I have searched existing issues
• I have reproduced the issue with the latest release

Area

admin/ui

Describe the bug

Admin Console at /master/console/#/{realm}/clients/{id}/keys. Tried to import client certificate pem file for the "Signing keys config". Instead of updating "Signing keys config" certificate the "Encryption keys config" certificate was updated. No way to update the certificate for "Signing keys config" from the Admin Console.

Version

Keycloak Quarkus 20.0.2

Expected behavior

The client app certificate pem file is imported to the "Signing keys config"

Actual behavior

The "Signing keys config" certificate is not updated and remains as the default generated certificate.

How to Reproduce?

1. Log in to master realm
2. Navigate to application realm
3. Navigate to a SAML client on the keys tab at /master/console/#/{realm}/clients/{id}/keys
4. Attempt to import certificate for "Signing keys config"

Anything else?

Currently the workaround is to disable the "Signing keys config" client signature.
Can anyone provide the commands to update the "Signing keys config" certificate using api?

[ssilvert]

I have verified that the new console is calling the wrong API. It is calling /certificates/saml.encryption/upload instead of /certificates/saml.signing/upload.

Moving issue to keycloak-ui repo.

[ssilvert]

@wilderk As a workaround until this is fixed, you can use the old admin console. Just go to Ream settings -> Themes and change the admin theme to keycloak. The refresh your browser.

[wilderk]

Thanks @ssilvert. I confirmed the workaround by changing the "Admin Console Theme" in the "master" realm to the old "keycloak" theme.

[edewit]

okay this UI might be a bit strange, but in order to upload the signing keys you should first disable Client signature required and then turn it on again. Only the a dialog will appear to import the signing keys:

[wilderk]

@edewit - This issue is not about whether or not the import dialog is visible. There is a confirmed problem in the code. The wrong API is being called.

[edewit]

@wilderk yes you are right, I was confused, let me fix that right now