[Kolab-devel] enlargement of kolab ldap schema for asp service

[Thomas Börnert]

> We could think about making a subtree within the private OID space,
> which we could reserve for experimental attributes.
> On the other hand, maybe it might be easier to just apply for your own
> private OID space for experiments. This is fairly simple as far as I
> remember.
>
> Thanks for the summaries and the comments, I am still making up my mind
> about how to do this all best.
>
> What strikes me as important is that some of the measures should be
> controlled in the underlying software, not the web-frontend. In the current
> design it would be allowed for the customers to connect to the ldap server
> itself, give their credentail and just change the attribute they can.

ok, right ..... in the first step i would not allow ldap access.
imho i think the customer need only access to the adressbook,
not to the domain manager object and not to the domain object, right ?

>
> So how with your web-cyradm would you enforce the options?

web-cyradm don't use ldap, it uses mysql.

Thomas