From: Terefang V. <ter...@gm...> - 2015-06-12 10:19:28
|
hi! On Fri, Jun 12, 2015 at 11:04 AM, Krzysztof Benedyczak <go...@ic...> wrote: > > OK, so rest API is here a way to go. Note that 'loading on startup' is bit > more confusing, as it work as expected during the first start and can mess > your setup after subsequent restart (e.g. if you manually fixed one > attribute type and then after restart you get the old definition). > > So yes, this is pretty easy to be added to the REST API, can go into > 1.7.0. What is another low hanging fruit is a possibility to import > attribute type definitions directly from LDAP schema. The converter is > implemented in Unity but not exposed. I can enable it if you find this > useful. > the rest api is definitely the way to go, as the attribute definition may be more complex than what simple ldif is capable of. i agree, if one could do a simple http-post with a ldif-schema in the body, a lot of people would be satisfied with it. the question is rather what subset or extension of ldif do you want to support, without being a pain for average users. for example "ENUMS": about 50% of attribute definitions i use (that dont map directly to ldap) are enums. in your case you might at least support X-ENUM and X-PATTERN, for compatiblity ( see http://docs.forgerock.org/en/opendj/2.6.0/admin-guide/index/chap-schema.html#attr-syntax-schema-definition-extensions ) cheers, -- Terefang |