Hi Oli,
how big is your LAM server profile file? You can find it in
/var/lib/ldap-account-manager/config/NAME.conf
Maybe there can be a small change possible to support larger amounts of
custom fields.
In general, custom fields is designed to be used when you have a few
extra fields but not 100. Here the best way is to go using a custom
module. This also allows additional functionality such as custom
validations, access to LDAP for data display, ...
Custom modules are written as a separate file and added to LAM. This way
there are no issues in upgrading LAM. Also, the API rarely has changes
that are not backwards compatible.
Just in case you want to go this way we offer custom module
implementation on a fixed price basis.
Or, implement on your own using the docs you already found. Try to copy
a small existing module as a starting point.
Best regards
Roland
Am 09.07.21 um 09:28 schrieb Oliver Becker:
Hi,
I noticed limitations to the custom fields:
When I tried to config in LAM Pro 7.3 more than 100 LDAP attributes (I
think it was 103 in real), it stopped changing the server profile.
With LAM Pro 7.6 and its option to use mysql I hoped, this limit would
be obsolete. Unfortunately the limitation went down to 32 attributes
what makes LAM not useful for me.
Are there some changes to do in general settings that might change this
limitations?
Is there a way to get over this by using custom made modules?
I tried a bit using this link:
https://www.ldap-account-manager.org/static/doc/devel/mod_index.htm
But I didn't get my test working.
I think the main problem is the "customFields_fieldList"-subset which is
really huge. Maybe this could be transfered in a different table and
become more handy.
Best regards
Oli
Oliver Becker
_______________________________________________
Lam-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lam-public
_______________________________________________
Lam-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lam-public
