pluggable templates
by Bill Burke
Was thinking about pluggable templates for login, oauth screen, user
acct mgmt, etc...
Why force users to use Freemarker? Why not allow them to create a
directory within the Keycloak Server WAR and use whatever framework they
want to use? Then to choose a template, you just specify the URLs for
login, oauth, user acct mgmt, etc?
What sucks is, because we're using Freemarker and everything is bundled
up in JARs, there's no easy way for users to copy/paste a template and
create and play with their own on the fly.
Just food for thought for after Alpha 1 release.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
11 years, 11 months
full export support
by Bill Burke
Was thinking about full export (including credentials) of a realm.
Maybe we could allow this through the admin console, but the export is
dumped to a local directory on the server. That way, only somebody with
access to the server can obtain the dump.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
11 years, 11 months
Feedback on examples
by Marek Posolda
I have few points regarding example applications:
- For third-party oauth client example, there is not possibility to
configure stuff through JSON but everything is hardcoded in classes
Bootstrap and ProductDatabaseClient. There are also some strange
comments in code like "This is the worst code ever" etc :-) This is not
so ideal IMO as I expect that people will often look to the source code
of these examples for inspiration. I believe that OAuth clients should
also have something like ManagedResourceConfigLoader for Applications.
- For the "third-party" OAuth client, I don't like the fact that when
user press "Cancel" in OAuth grant page, there is exception in
server.log and Tomcat error page displayed. I believe the behaviour
should be more user-friendly.
- Examples "customer-portal", "product-portal", "database-service" and
"oauth-client" are using package "org.jboss.reasteasy..." instead of
"org.keycloak..."
Any thoughts? Let me know if I should create JIRA or help with fixing those.
Marek
11 years, 11 months
require adapter modules?
by Bill Burke
Rather than have multiple options for installing a as7 or wildfly
adapter, do you think its fine to require the installation of jboss
modules for your desired adapter then adding a
jboss-deployment-structure.xml to your deployment?
* This avoids any dependency conflict between a keycloak adapter and the
application.
* The distribution becomes smaller as I don't have to include both
jboss-modules zips and unpacked jars.
* Less options is also less confusing. Having too many options can be
confusing
* We can always document later how to pull in libs directly to the
deployment.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
11 years, 11 months
