CORS error with 26.0.6 when hostname and hostname_admin are different

[olivier34000]

Hello,

I updated the container from 25.0.6.1729619380 to 26.0.6.1732296619 and now in the admin area of Keycloak when I click on Organizations I have a cors issue CORS error fetch useOrgFetcher.ts:30

The variables KC_HOSTNAME and KC_HOSTNAME_ADMIN are different. I tried to keep the old variables KC_HOSTNAME_URL and KC_HOSTNAME_ADMIN_URL but it doesn't work.
The request on /realms/master/orgs?first=0&max=11 is executed on KC_HOSTNAME instead of KC_HOSTNAME_ADMIN

Could you check ?

[xgp]

@pnzrr There is a change because of the "hostname v2" update. Can you check to make sure we are honoring the new variable names when constructing the orgs API urls? https://www.keycloak.org/server/all-config#category-hostname_v2

[pnzrr]

@xgp this is currently set with:

const authUrl = environment.serverBaseUrl;

so I can try to adjust using the newer

const authUrl = environment.adminBaseUrl;

and hope that will pick up the right url.

[pnzrr]

https://github.com/p2-inc/keycloak/tree/26.0.6_orgs_admin_ui

[xgp]

@olivier34000 can you please try the image that was released yesterday? 26.0.6.1732738384

[olivier34000]

@xgp I checked the new release but it doesn't work. I restored Keycloak with the version 25. With KC_HOSTNAME_ADMIN_URL and KC_HOSTNAME_URL it worked well. However KC_HOSTNAME_ADMIN and KC_HOSTNAME it didn't work.
With the verison 26 KC_HOSTNAME_ADMIN_URL and KC_HOSTNAME_URL doesn't work anymore as explained in the docs https://www.keycloak.org/docs/26.0.6/upgrading/#new-hostname-options