I am playing with the deployment to add the ability to deploy the whole system with a user that hasn't root privileges.
That said, I noticed something annoying. After I managed to set up everything (locally and with my username instead of root). I opened my browser to check the web app and got this after I tried to log into the website:
ldap.SERVER_DOWN: {'result': -1, 'desc': "Can't contact LDAP server", 'errno': 11, 'ctrls': [], 'info': 'Resource temporarily unavailable'}
In the config, I specifically left the LDAP server setting empty. Because the app settings, do set the DKRZ server if it is not set at all.
a) Why is this pointing to the DKRZ LDAP server by default?
b) How can I tell the thing not to use ldap at all?
To me, it would be more natural if the thing would try to talk to any LDAP instance unless not specifically told to do so.
I am playing with the deployment to add the ability to deploy the whole system with a user that hasn't root privileges.
That said, I noticed something annoying. After I managed to set up everything (locally and with my username instead of root). I opened my browser to check the web app and got this after I tried to log into the website:
In the config, I specifically left the LDAP server setting empty. Because the app settings, do set the DKRZ server if it is not set at all.
a) Why is this pointing to the DKRZ LDAP server by default?
b) How can I tell the thing not to use ldap at all?
To me, it would be more natural if the thing would try to talk to any LDAP instance unless not specifically told to do so.