index c2cfb360de3e2e8e0810c7f9d454870bc45654f6..697f75363bff36f53953ed77e49bfb74fd3a4650 100644 (file)
--- a/FAQ
+++ b/FAQ
A: Yes. Just set "account_expiration" to "true" in your gosa.conf's main section.
-Q: How can i activate the object snapshot functionality?
-
-A: Add these lines in the main section of your gosa.conf
- enable_snapshot ="true"
- snapshot_base ="ou=snapshots,dc=server,dc=de"
-
-
-Q: How can i store object snapshots on another server?
-
-A: Just add these lines in the main section of your gosa conf
-
- snapshot_ldap_base ="dc=server,dc=de"
- snapshot_user ="cn=ldapadmin,dc=server,dc=de"
- snapshot_password ="password"
- snapshot_server ="ldap://server:389"
-
Q: What is the correct connection string for a Kolab server in GOsa?
A: For Kolab to work correctly you have to include the rfc2739.schema
in your slapd.conf. Insert it before the kolab2.schema
+
+Q: Is there a way to let GOsa automatically fill missing fields in the network
+ configuration?
+
+A: Sure. You can specify the "auto_network_conf" option and provide the contributed
+ script "net-resolver.sh" in your gosa.conf. If this is configured, you're
+ getting an additional button in each network dialog.
+
+
+Q: New implementations of OpenLDAP seem to require {sasl} instead of {kerberos}
+ in password hashes. GOsa writes the wrong string. What can I do?
+
+A: You can set "krbsasl" to "true" in your gosa.conf's main section.
+