An example custom login theme based on keycloak/login with a custom footer could look like this:

theme.properties:

parent=keycloak
import=common/keycloak
styles=css/login.css css/custom-login.css

resources/css/custom-login.css

#kc-login-footer-links {
    text-align: center;
}
#kc-login-footer-links li{
    display:inline-block;
}

footer.ftl file:

<#macro content>
    <!-- hello from footer.ftl -->
<div>
	<#-- footer at the end of the login box -->
    <hr id="kc-login-footer-divider">
    <ul id="kc-login-footer-links">
        <li><a href="https://apps.training.test/apps/site#home">Home</a></li>
        <li><a href="https://apps.training.test/apps/site#about">About</a></li>
        <li><a href="https://apps.training.test/apps/site#services">Services</a></li>
        <li><a href="https://apps.training.test/apps/site#contact">Contact</a></li>
    </ul>
<div>
</#macro>

WIth login-footer links we get the following result:

With Identity Providers:

Great idea!
After looking at the result, would it be possible to also add a (page) footer at the bottom of the page (instead of the "login form")?
There you could add other things (like a copyright notice) without making the login form look overcrowded.

@cturkalj I thought about that too. How about the following:

login-footer.ftl contains a macro that's rendered at the end of the "login box" (like my current footer.ftl above).
footer.ftl contains a macro that's rendered at the bootom of the page as you suggested.

Both macros would be empty by default.

Would that work for you?

@edewit thanks for your review! What do you think about the suggestions from @cturkalj?

@thomasdarimont:
Perfect, thank you!

I did a small example for the suggested extension:
https://gist.github.com/thomasdarimont/8021ef4bf715aae2cb28ca2ca3151ab7#file-template-ftl-L169

It contains a two footer templates:

• footer.ftl -> Inserted at page bottom and content will be wrapped in a <footer> element
• login-footer.ftl -> Inserted at login box bottom and content will be wrapped in a <div id="kc-login-footer"> element
  Thoughts?

If that's okay, then I'd update this PR.

I updated the PR based on the suggestions. I now use an empty footer.ftl and login-footer.ftl templates by default.
Users have full control over the template fragment contents.

Allthough I think the footer.ftl will rarely be used, because the login-footer.ftl is IMHO sufficient for many scenarios already. However, users might use the footer.ftl to include javascript add the very bottom of the page if necessary.

Added note to release notes

@thomasdarimont - there is a conflict with the release notes. Please rebase and resolve.

@ahus1 Thanks for the review. I rebased the PR and resolved the conflict.

I also added support for the custom footer(s) to the login.v2 theme which I learned will become the default login theme from now on.

However, there are some issues with the login theme v2 which I mentioned on the maintainers mailing list. So I'd recommend to wait for feedback from the other maintainers before merging this PR.

I also tested this with the keycloak.v2 login theme.

Theme minimal.v2/login, see: https://gist.github.com/thomasdarimont/5fe725319a5fc3c8242669deddd934a8

Custom theme based on Login V2 with empty Footer

Custom theme based on Login V2 with Footer

Custom theme based on Login V2 with Identity Providers and Footer

@cturkalj I experimented a bit further with the footer customizations and I think it would be sufficient to only have one footer.ftl file that we add at the bottom of the login box. Links that should be shown at the bottom of the page can be moved there via CSS. This would make the templating easier, as the current login page styling of the keycloak and keycloak.v2 theme does not support adding links outside of the "login box" anyways.

Can you think of something that would not be possible if we only had one footer.ftl ( the login-footer.ftl in the current examples)?

If there are no issues then I adapt this PR and only keep the login-footer.ftl file.

@thomasdarimont:
I was able to use the login-footer.ftl only and have the footer at the bottom of the page with css (thanks for the hint).
Besides that, I currently don't have in other use cases in mind.

Now that we have just one (login)-footer.ftl left, should it be renamed it back to footer.ftl?

I revised the PR to only contain 1 additional template file -> footer.ftl

• Added section to the release-notes
• Added section to the upgrading guide
• Added section to the themes section in the server development docs