<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Perhaps it's a little early to start implementing a Keycloak FP, but
I'm starting to look at it and identify potential issues. So I
thought I should list the issues here and find out which ones are
already addressed and which need some time to work out.<br>
<br>
<b>Task:</b> Implement a feature pack that adds the Keycloak Auth
Server to either/both of the <u>WildFly Web build</u> and the <u>WildFly
Full build</u>. <br>
<br>
Note that this is completely separate from the effort to use
Keycloak to secure the web console. That only involves Keycloak
adapter integration destined to ride on top of Elytron. <br>
<br>
Here, we are talking about using a feature pack to add and configure
the Keycloak Auth Server.<br>
<br>
<b>Issue #1: Module duplication.</b> Keycloak needs to install the
bouncycastle module. This module already exists in the full build
but not the web build. So you have the same module specified for
the Keycloak FP and the Full WildFly FP.<br>
<br>
I assume this is already handled? Will the FP mechanism have a
problem with duplication of modules when I try to add a module to
full that already exists?<br>
<br>
<b>Issue #2: Adding a subsystem:</b> It looks like the current
mechanism for creating configuration files is inappropriate for the
Keycloak FP. The way this is done right now is that a config file
is generated via the combination of a template file and a list of
subsystem snippets. So you would have, for example:<br>
<br>
template-keycloak.xml + subsystems-keycloak.xml =
standalone-keycloak.xml<br>
<br>
But that's not what we really want. We don't want a separate
standalone-keycloak.xml. We really just want to add the keycloak
subssytem to every generated config file, whatever they may be.<br>
<br>
<b>Issue #3: Adding a deployment:</b> The Keycloak auth server is
deployed as a WAR. We can use the copy-artifacts mechanism to
simply copy the WAR into the deployments directory. But that
doesn't work for a domain where you want to have the WAR pre-loaded
into the content repository. Furthermore, it's probably not the
best way to integrate this for standalone either.<br>
<br>
What would be a better option?<br>
</body>
</html>