Styling a page from custom Freemarker Template

[waynemorphic]

I have gone through the explainer on Styling a custom page but I have yet to get an idea or solution for my problem. I have a custom Freemarker template, call it preferences.ftl, that is not included in the Keycloak Base template or as a Phase Two plugin, which contains cookie preferences and language options for my users. I would like to include it in the login and register pages. How do I go about it?

[garronej]

Hello,

If you share more details I can give you more precise instructions

[waynemorphic]

Hello @garronej I sort of figured out where to place it within the Template.tsx file. However, could you help with pointers on where I can place cookie consent based on this CookieConsent plugin?

[garronej]

Hello @waynemorphic,

I don't think you should put you cookie consent policy on the keycloak login page.
This belongs on your app.

[waynemorphic]

I want the cookie consent banner to appear as a modal on my login and register pages. Can this be added to the Template file?

[garronej]

I strongly recommend you don't do that unless you precisely understand why you're doing it this way. It's not common at all to implement cookie consent directly on the Keycloak login page, and here’s why:

1. Separate Domain for Login: Keycloak pages are typically hosted on a different domain than your main application. This means if you implement cookie consent on the login page, the user would likely need to give consent again on the main application, which is redundant and could lead to a frustrating user experience.

2. Cookies Set by Keycloak: The cookies set by Keycloak during the authentication process are generally related to session management and do not require user consent. These cookies are exempt from consent requirements in most privacy regulations, unless you've added specific features that require tracking or analytics.

3. Best Practice: The consent for cookies should ideally be handled in the main application where the cookies for analytics, tracking, and third-party services are being set. This ensures that the consent mechanism is centralized, and avoids redundant requests across domains.

In conclusion, unless you have a very specific need for handling cookie consent on the Keycloak login page, I suggest you consider handling it on the main app instead.

[waynemorphic]

Awesome, thank you for your detailed feedback @garronej