79 * `cache-life-time`, life time of query cache in minutes (default to two hours). |
79 * `cache-life-time`, life time of query cache in minutes (default to two hours). |
80 |
80 |
81 Other notes |
81 Other notes |
82 ----------- |
82 ----------- |
83 |
83 |
84 * Yes, cubicweb is able to start if ldap cannot be reached, even on c-c start, |
84 * Cubicweb is able to start if ldap cannot be reached, even on |
85 though that will slow down the instance, since it will indefinitly attempt |
85 cubicweb-ctl start ... If some source ldap server cannot be used |
86 to connect to the ldap on each query on users. |
86 while an instance is running, the corresponding users won't be |
|
87 authenticated but their status will not change (e.g. they will not |
|
88 be deactivated) |
87 |
89 |
88 * Changing the name of the ldap server in your script is fine, changing the base |
90 * Changing the name of the ldap server in your script is fine, changing the base |
89 DN isn't since it's used to identify already known users from others |
91 DN isn't since it's used to identify already known users from others |
90 |
92 |
|
93 * When a user is removed from an LDAP source, it is deactivated in the |
|
94 CubicWeb instance; when a deactivated user comes back in the LDAP |
|
95 source, it (automatically) is activated again |
|
96 |
|
97 |
91 * You can use the :class:`CWSourceHostConfig` to have variants for a source |
98 * You can use the :class:`CWSourceHostConfig` to have variants for a source |
92 configuration according to the host the instance is running on. To do so go on |
99 configuration according to the host the instance is running on. To do so go on |
93 the source's view from the sources management view. |
100 the source's view from the sources management view. |