Running a pre-release?
by Phillip Johnsen
Does anyone have any hints about possibly running a CR version or even directly off the master branch?
The migration docs says the following:
Migration from a candidate release (CR) to a Final release is not supported. We do however recommend that you test migration for a CR so we can resolve any potential issues before the Final is released.
Which in reality answers my question, but is it really impossible in theory? I'm not too familiar with Keycloak yet, so any hints about possible consequences and / or tricks would be great.
To elaborate more about my actual need; we're developing a product that has a hard requirement on the recently merged Paypal integration: https://github.com/keycloak/keycloak/pull/4449
We have utmost respect for recent changes not beeing added and stressed into future releases, so we want to double check if there's anything we can to do run Keycloak with those changes even though a final version including Paypal hasn't been published yet. We do acknowledge we're taking some risk by possibly running a pre-release, though that might be worth it for us, as long as we don't create a massive challenge for ourselfs down the road.
Any hints or thoughts would be much appreciated!
Thanks,
Phillip
7 years, 2 months
spring-boot-2 - new artifact suggestion
by James Green
Hi,
We have a problem in that we are trying to integrate future spring-boot-2
projects with Keycloak but there are binary compatibility problems.
May I suggest someone adds a new spring-boot-2 adaptor so that
compatibility with both can be maintained?
Thanks,
James
7 years, 2 months
Overriding Cookie Paths
by John D. Ament
Hi,
I noticed in OAuthRequestAuthenticator that the cookie path being set is to
null. From what I can tell, this means in most containers if my first
release is to /foo/bar/baz/bar that the path saved to the cookie is
"/foo/bar/baz". This is typically not an issue, however I have a legacy
app I'm trying to integrate with Keycloak, so the cookie state is very
important. By setting the path to a low level when I later access
/foo/home.xhtml it causes the cookie to not get populated (which causes a
400 bad request later on).
I'm wondering, does it make sense to add something to KeycloakDeployment
that lists the cookie path, defaulting to null if its not set.
John
7 years, 2 months