The structure of our details code is basciallt
[categorid, categoryDisplay, atrrtibutes]
and attributes are
I've inlined the user details at the bottom as an example.
In order to make these configuratble by the end user, here is a strawman
Create a dir under /var/lib/ipa/details with code that will, at run
time, get validated and then appended to the web code. This code,
unlike the resources approach, will not be autogenerated.
The code for the user details gets pre-populated there from a
static copy somewhere under /usr/share/ipa. The end user can then
customize it to add or remove fields.
provide more advanced UI. An example might be a n interactive map for
showing seat and parking assignments.
IPA server install and uninstall will be aware of these files, and
treat them gently. Doing an install will not over write the files if
they are present, but will instead rename and back them up. Same with
uninstall, unless an additional option is given ( for example
--ultraclean) the is repsonbile for removing all vestiges of IPA from a
The details pages will be named <collection>-details.js:
user-details.js, group-details.js and so forth.
As I said, this is a strawman. Please poke holes in it, and make better
var user_details_lists = [
['identity', 'Identity Details', [
['givenname', 'First Name'],
['sn', 'Last Name'],
['cn', 'Full Name'],
['displayname', 'Dispaly Name'],
['account', 'Account Details', [
['call_a_status', 'Account Status'],
['contact', 'Contact Details', [
['mail', 'E-mail Address'],
['address', 'Mailing Address', [
['employee', 'Employee Information', [
['ou', 'Org. Unit'],
['misc', 'Misc. Information', [
['carlicense', 'Car License']
Freeipa-devel mailing list