Closed paulwer closed 1 year ago
I think the error comes from config.ts - Line 99
old keycloak instances has used the /auth prefix. any chances to fix this in the next release?
@xgp is there an upcomming change for us in the pipeline?😊
@paulwer Customers are all using /auth
relative path URL so this is low priority. Feel free to PR the fix.
@xgp i added a simple check, if the pathname includes /auth/ or not, to support old / your versions and newer keycloak versions, when installing from dockerimage
please test, if this is not suiteable for you, you/we may have to considder take a look at the public docker image, why the portal is there visiable at /realms and not /auth/realms. what do you think?
Thanks. I merged, and I'll take a look when we release a new public docker image. TBH there's a lot of cases where we assume that /auth
will be the relative path, as most of our work started before Keycloak removed that necessity. Because of that, our hosted version, and all of our customers use it. I'd like to wave a magic wand and have it fixed everywhere, but I'm afraid it will be a game of whack-a-mole for people that are using no/another relative path.
@xgp i read this at keycloak before. maybe its time to migrate your applications to this new standard also. Or to implement at least the same behavior within the oss docker image.
Shall anyone create an issue / feature request out of this?
when opening the admin-portal at: https://phase-two-instance.com/realms/master/portal/ the resources are fetched from:
the right url would be: (without /auth, checked the urls and they serve files)
have I did something wrong within my configuration or is this a bug?
an other header is: