On 14. 11. 19 20:28, Stan Silvert wrote:
Fixing the slash was no problem but it looks like something else is
broken. Trying to initialize Keycloak, it gets a 400 error when it's
14:21:45,918 WARN [org.keycloak.events] (default task-24)
type=CODE_TO_TOKEN_ERROR, realmId=master, clientId=account, userId=null,
On 11/14/2019 6:56 AM, Stian Thorgersen wrote:
> Yes, this was changed due to default hostname provider.
> Stan do you need the auth-url or a URL to something else? If the
> latter the safest is to use the builder to get the path, unless you
> are doing that on the client side.
> On Thu, 14 Nov 2019 at 10:07, Jan Lieskovsky <jlieskov(a)redhat.com
> <mailto:firstname.lastname@example.org>> wrote:
> On Wed, Nov 13, 2019 at 10:46 PM Stan Silvert <ssilvert(a)redhat.com
> <mailto:email@example.com>> wrote:
> In new account console, I pass the auth URL to Freemarker. I
> This has always returned something like
> However, the latest in master puts a slash at the end,
> I can easily update my code for this to work, but I'm
> concerned that
> this change might have broken more than just the new account
> Perhaps other code in the community is relying on the URL not
> having a
> slash at the end.
> Does anyone recognize the change that might have caused this?
> Might be related with the recent new default hostname provider
> (KEYCLOAK-11728) change.
> At least this change in corresponding test acceptance criteria
> would suggest so.
> But given the corresponding test was changed to expect slash at
> the end, I would say this
> is expected behaviour now. @Stian Thorgersen
> <mailto:firstname.lastname@example.org> Can you confirm?
> Thank you && Regards, Jan
> Jan iankko Lieskovsky / Keycloak / RH-SSO Team
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org <mailto:email@example.com>
keycloak-dev mailing list