Hi all, I created a simple LDAP client on top of ldap3, as our ldap_store_attributes MS is. https://github.com/peppelinux/pyLDAP I think that would be better to handle all the configuration parameters subdivided as API methods are implemented, like https://github.com/peppelinux/pyLDAP/blob/master/settings.py.example#L4 At this moment we maps them manually from configuration to ldap_store MS, that approach instead would permit us somethig like: https://github.com/peppelinux/pyLDAP/blob/master/client.py#L32 https://github.com/peppelinux/pyLDAP/blob/master/client.py#L41 things will come as they are from yaml configuration, without any additional mapping into MS code. Another topic is the possibility to decouple standalone clients from MS, as guidance principle. The tool I showned can fetch data from multiple sources using a single configuration. I can be also apply embedded rewrite rules. Doing it in the client and using that client decoupled from MS code would be better to debug and app/code reuse. In the MS code we would only include calls to the client's API, to get them to work and fetch from them what needed. They could also scale up in a multiprocessing asset more easily this way. Multiple clients, with same methods and similar API could be parallelized for a faster data aggregation and account linking. The same methods could be used for a WS service with SOAP client, noSQL client and others. these thought would be also be linked to our latest comments about the "global configuration visible into MS" and "a shareble context into MS", if these ideas could help in a wider approach with potential benefits for the future. I share as it is, see you back soon