----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Friday, February 20, 2015 3:15:19 AM
Subject: [keycloak-dev] How to render claim data entry and display?
I'm not sure how to render claims within the admin console, registration
page, and in the user self service pages. The thing is that generically
rendering user metadata can look quite ugly. Address is one example
where the grouping and ordering of each attribute is important to look
nice. There are other instances where you need to group types of data
together (home phone, fax, work phone, mobile). Then there is the
problem of what claim data do you show on what pages which is harder
than it seems, for example, registration page might only require a
mobile number, but admin console and user profile page might want to
show home, fax, work too. You would end up having to define a data
model that captured metadata for each page type (registration, user
profile, and admin console). Finally, if you have generically rendered
claims, what happens when the user wants to override this rendering and
put their own formatting, .css types, etc. in?
This leads me to think that we should just punt to the developer. In
this case, there would be no data model for claim types and everything
would be driven simply off of UserModel.attributes. Develoeprs would
have to extend the admin console and account themes and we would provide
a template for referencing UserModel.attribute data within Angular HTML
(admin console) or Framemaker (account service, registration page).
For registration page and account management I think supporting simple attributes in the
default template would be good enough. Users can then extend the templates if they need
something more. In the future we can look into creating widgets that can display certain
things so users don't have to extend the whole template, but just parts of it.
For the admin console it would be best not to require users to extend IMO. We should be
able to allow users to view and edit complex attributes (at least a complex attribute that
is a list of simple, rather than complex of complex). Initially we could just display the
JSON for the complex attribute directly, then create an view/editor for it later.
I know Stian talked about validation, but I think this could be added on
after the fact via an AttributeValidator and again tied to a specific
UserModel.attribute.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev