templates for version 2

[scholl]

hi,

i really like you're work! short question for v2 is there a time plan when templates are available?
this was a really helpful feature in v1 :)

BR
Tobi

[leenooks]

Howdy, I'm actually thinking about the templates next.

My initial plan was that templates would work slightly differently in v2. In v1, templates enforced an entry to meet the requirement of the template - and thus would remove attributes that were not referenced.

In v2, I'm thinking of using templates to make attributes available around common usage, thus:

• An entry may have more than 1 template, eg: posixAccount for for unix account management, and maybe inetLocalMailRecipient, for mail management.
• Templates will still guide default values as before (and perhaps enforce attribute values)

I'm thinking of how the UI will make them available, selectable and apparent (on an existing entries). They would also be configurable using JSON instead of XML (so v1 templates could not work with v2).

I'm keen to hear other thoughts and suggestions.

[scholl]

sounds great to me, from my side a issue from v1 was that when an entry was created and the "default" view was disabled after creation of an entry not the template was showen but the default view with to many attributes. This was confusing for some admins. Only after a reload there was the template showen.

[3eka]

I have (maybe) missed info: how to start with templates?

[3eka]

Ah. Never mind - was expecting option to SPECIFY template ...

I see now, looks like I have just to create JSON file and it is auto magically picked-up ...

Thanks

P.S:
Still, I would like to read docs how to build template... Any hint?

[3eka]

Hi again,

I was playing with templates:

• added own one (basically, wanted to show some attributes, but no allow editing; also added custom schema objectClasses)
• disabled mail_account and user_account

Issues:

• "order" value is not obeyed
• I could get rid of disbled mail_account and user_account templates only after re-running npm and compose commands (seems those are cached?)
• Where I can disable "template" shown under name LDAP Entry (I do not want users to accidentally change/delete some attributes)?
  ** It allows all attributes to be edited/removed thus ignoring LDAP ACI defined for attributes which are supposed to be edited by user (e.g. "Enable self write for common attributes" rule), causing confusion a.k.a. "why is my attribute value still there, although I have removed it"

Best regards.

[leenooks]

I could get rid of disbled mail_account and user_account templates only after re-running npm and compose commands (seems those are cached?)

Yes, PLA caching a few things (including templates, queries and view rendering). To clear the data cache (which the templates are stored in), you can issue php artisan cache:clear

Where I can disable "template" shown under name LDAP Entry (I do not want users to accidentally change/delete some attributes)?

A templates are either enabled or not - there are no per user controls. If you want to stop users from updating entries, then you need to have those rules in your LDAP server. PLA does not perform any authorisation activities - see the wiki.

[3eka]

I have configured ACI which prevents user for changing some attributes (kerberos principal for example), but in LDAP Entry "template" everything IS allowed, although not possible.

Anyway, I will instruct users to use different template for editing.

Regards.