Updated FAQ

git-svn-id: https://oss.gonicus.de/repositories/gosa/trunk@5856 594d385d-05f5-0310-b6e9-bd551577e9d8

diff --git a/FAQ b/FAQ
index 30b4c8e340d10420ae00365c4f35c626d2c6844a..f9a13dbf9ae1816520bee1c01495a9efffe72434 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -312,22 +312,6 @@ Q: How can i active the account expiration code for the gosa interface?
 
 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?
 
@@ -351,11 +335,17 @@ A: For Kolab to work correctly you have to include the rfc2739.schema
 Q: Is there a way to let GOsa automatically fill missing fields in the network
    configuration?
 
-A: Sure. You can specify the "autoconf" option and provide the contributed
+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.
+
+
 Q: Is there a way to add the personalTitle attribute the the users dn?
 
 A: Just add this line into the location section of your gosa.conf.
@@ -363,3 +353,10 @@ A: Just add this line into the location section of your gosa.conf.
        include_personal_title="true"
    ...>
 
+
+Q: I'd like to assign different uid bases for certain user/group objects.
+   How can this be achieved?
+
+A: Use the base_hook in your gosa.conf's location section to specify a script
+   which handles the ID generation externaly. It get's called with the "dn"
+   and the attribute to be ID'd. It should return an integer value.