-
|
Hi, After Login in to https://domain.com/admin/realmA/console/ I see the following error in my browser logs:
I have tried to add Web Origins to my relamA security-admin-console but technically I would need to add my realmA domain to the serverinfo clients Web Origins. Unfortunately, it seems that there is no configuration for it. Has anyone dealt with the same problem or can help me otherwise? Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
OK I found the solution. I knew it must have been a misconfiguration, but I was looking at the wrong spot. My Masters Realm FrontendURL is set to: in my keycloak.conf I defined: The solution was to remove I misunderstood its function. This would set the Admin URL for each Realm to exactly this URL not just master relam. I obviously didnt had any problems in my masters realm. but once I tried using the MyRealm Admin Console, its API and Admin Request where set to this this instead of the frontendURL set via the console. Trying to access https://22.22.22.11:8443/auth from https://domain.com/auth triggers the CORS Error. After removing it the Admin URL is dynamically set to the Realm FrontendURL, hence all request use the same URL and no CORS situation happens. I realised that in also effected other Admin Requests like: |
Beta Was this translation helpful? Give feedback.
OK I found the solution. I knew it must have been a misconfiguration, but I was looking at the wrong spot.
My Masters Realm FrontendURL is set to:
https://22.22.22.11:8443/authMy MyRealm FrontendURL is set to:
https://domain.com/authin my keycloak.conf I defined:
The solution was to remove
hostname-admin=https://22.22.22.11:8443/authI misunderstood its function. This would set the Admin URL for each Realm to exactly this URL not just master relam. I obviously didnt had any problems in my masters realm. but once I tried using the MyRealm Admin Console, its API and Admin Request where set to this this inste…