Updated FAQ for new hook

[gosa.git] / FAQ

diff --git a/FAQ b/FAQ
index 3702b1cab80a3f4ceee1f85dfe80bc4c55abcc86..59583dde1d51864ce35a308195c2a3ba47488d65 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -269,12 +269,12 @@ Q: I'd like to have TLS based LDAP connections from within GOsa. Is this possibl
 
 A: Yes, add
 
-   <main ...>
+   <location ...>
    ...
          tls="true"
    ... \>
 
-   to the main section of GOsa. This switch affects all LDAP connections.
+   to the location section of GOsa. This switch affects LDAP connections for a single location only.
    
 
 Q: Cyrus folder get created in the style user.username. I prefer the unix hirachy
@@ -312,28 +312,51 @@ 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: What is the correct connection string for a Kolab server in GOsa?
+
+A: Try {localhost:143/novalidate-cert}.
 
 
-Q: How can i store object snapshots on another server?
+Q: Sieve is not working from GOsa - there are authentication problems
+   with this service, IMAP/POP is working. What's wrong?
 
-A: Just add these lines in the main section of your gosa conf
+A: Verify that the paramater sasl_auto_transition: no is not
+   present in your imap.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
+Q: Slapd does not start with kolab2.schema included. It claims that the
+   definition of calFBURL is missing. What can I do?
 
-A: {localhost:143/novalidate-cert}
+A: For Kolab to work correctly you have to include the rfc2739.schema
+   in your slapd.conf. Insert it before the kolab2.schema
 
-Q: Sieve is not working from GOsa
 
-A: verify that the paramater sasl_auto_transition: no is not
-   present in your imap.conf
+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.
+
+
+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.
+   <location name=...
+       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.