fix(KcAccountUiLoader.tsx): authUrl can be a string

[jspizziri]

there are cases in which authUrl can be a string. In these cases the serverBaseUrl currently throws because authUrl.rawSchemeSpecificPart is undefined and therefore authUrl.rawSchemeSpecificPart.replace is an invalid access.

[jspizziri]

@garronej just an FYI on this. This is causing issues on keycloak 21.1 when a Frontend Url is set.

[garronej]

Very nice thank you very much!

[jspizziri]

Thanks for the merge! Any general thoughts on when this might be released?

[garronej]

I just did 25.0.4-rc.6

[jspizziri]

thank you sir!

[garronej]

NOTE: In the context of this package rc.6 does not mean release candidate. It's just an aditional version number that I use to version the compatibility layer code while still matching the version of the source package.

[jspizziri]

I'm also seeing some strange things happening with i18n when there's a Frontend URL. I'll try to look into it next week.

[garronej]

Thank very much, @jspizziri!
Your feedback is very helpful.

Just to clarify, as you likely understood, this package provides a compatibility layer, allowing the original package—designed specifically for Keycloak 25—to work with both older and future versions of Keycloak.

To achieve this, I infer the running Keycloak version based on the structure of the FreeMarker context and adapt (or polyfill) the API calls accordingly.

The approach I've taken is quite empirical, so there may still be some mistake here and there as you are experiencing. It's invaluable to get a hand from developers like you, who are deploying custom Account UIs on older Keycloak versions.