<?xml version="1.0" encoding="UTF-8"?>

<!--
    This file stores bootstrap properties needed by Wildfire.
    Property names must be in the format: "prop.name.is.blah=value"
    That will be stored as:
        <prop>
            <name>
                <is>
                    <blah>value</blah>
                </is>
            </name>
        </prop>

    Most properties are stored in the Wildfire database. A
	property viewer and editor is included in the admin console.
-->
<!-- root element, all properties must be under this element -->
<jive> 
  <adminConsole> 
    <!-- Disable either port by setting the value to -1 -->  
    <port>9090</port>  
    <securePort>9091</securePort> 
  </adminConsole>  
  <admin> 
    <!-- Use this section to define users that will have admin privileges. Below,
          you will find two ways to specify which users are admins. Admins will
          have access to the admin console (only local users) and may have also access
          to other functionalities like ad-hoc commands. -->  
    <!-- By default, only the user with the username "admin" can login
         to the admin console. Alternatively, you can specify a comma-delimitted
         list usernames that should be authorized to login to the admin console
         by setting the <authorizedUsernames> field below. -->  
    <!-- <authorizedUsernames></authorizedUsernames> -->  
    <!-- Comma-delimitted list of bare JIDs. The JIDs may belong to local
         or remote users. -->  
    <!-- <authorizedJIDs></authorizedJIDs> -->  
    <authorizedUsernames>@USER@</authorizedUsernames>
  </admin>  
  <locale>en</locale>  
  <!-- Network settings. By default, Wildfire will bind to all network interfaces.
      Alternatively, you can specify a specific network interfaces that the server
      will listen on. For example, 127.0.0.1. This setting is generally only useful
       on multi-homed servers. -->  
  <!--
    <network>
        <interface></interface>
    </network>
    -->  

  <!-- sasl configuration -->
  <sasl>
     <!-- Mechs to advertise. Order here should reflect
          preference advertised to client.  Just because
          you put it in this list dosnt mean it will be
          advertised either. If the authProvider cant support
          the mechanism, it wont be shown. PLAIN and ANONYMOUS
          mechs also enable non-SASL authentication (the old
          style XMPP auth), so removing them from this list
          will disallow non-SASL auth -->
     <mechs>GSSAPI,PLAIN,ANONYMOUS</mechs>
     <!-- <mechs>CRAM-MD5,DIGEST-MD5,PLAIN,EXTERNAL,ANONYMOUS</mechs> -->

     <!-- Several SASL mechanisms have a concept of a realm,
          but as of today only GSSAPI uses it. -->
     <realm>@UPPERDOMAIN@</realm>

     <!-- Mech specific configs here -->
     <gssapi>
        <debug>false</debug>
        <!-- GSSAPI needs its own config file -->
        <config>/opt/wildfire/conf/gssapi.conf</config>
        <!-- most will set useSubjectCredOnly to false (the default) See
             http://java.sun.com/j2se/1.4.2/docs/api/org/ietf/jgss/package-summary.html
             for more details -->
        <useSubjectCredsOnly>false</useSubjectCredsOnly>
     </gssapi>
  </sasl>

  <connectionProvider>
    <className>org.jivesoftware.database.DefaultConnectionProvider</className>
  </connectionProvider> 
  <database>
    <defaultProvider>
      <driver>org.postgresql.Driver</driver> 
      <serverURL>jdbc:postgresql://sql.@DOMAIN@:5432/wildfire</serverURL> 
      <username>wildfire</username> 
      <password>@WILDFIREPASS@</password> 
      <minConnections>5</minConnections> 
      <maxConnections>15</maxConnections> 
      <connectionTimeout>1.0</connectionTimeout>
    </defaultProvider>
  </database> 
  <ldap>
    <host>directory.@DOMAIN@</host> 
    <port>389</port> 
    <baseDN>@BASEDN@</baseDN> 
    <adminDN></adminDN> 
    <adminPassword></adminPassword> 
    <connectionPoolEnabled>true</connectionPoolEnabled> 
    <sslEnabled>false</sslEnabled> 
    <ldapDebugEnabled>false</ldapDebugEnabled> 
    <autoFollowReferrals>false</autoFollowReferrals> 
    <usernameField>uid</usernameField> 
    <vcard-mapping><![CDATA[
<vCard xmlns="vcard-temp">
  <N>
    <GIVEN>{cn}</GIVEN>
  </N> 
  <EMAIL>
    <INTERNET/> 
    <USERID>{mail}</USERID>
  </EMAIL> 
  <FN>{displayName}</FN> 
  <NICKNAME>{uid}</NICKNAME> 
  <ADR>
    <HOME/> 
    <STREET>{homePostalAddress}</STREET>
  </ADR> 
  <ADR>
    <WORK/> 
    <STREET>{postalAddress}</STREET> 
    <LOCALITY>{l}</LOCALITY> 
    <REGION>{st}</REGION> 
    <PCODE>{postalCode}</PCODE>
  </ADR> 
  <TEL>
    <HOME/> 
    <VOICE/> 
    <NUMBER>{homePhone}</NUMBER>
  </TEL> 
  <TEL>
    <WORK/> 
    <VOICE/> 
    <NUMBER>{telephoneNumber}</NUMBER>
  </TEL> 
  <TEL>
    <WORK/> 
    <CELL/> 
    <NUMBER>{mobile}</NUMBER>
  </TEL> 
  <TEL>
    <WORK/> 
    <PAGER/> 
    <NUMBER>{pager}</NUMBER>
  </TEL> 
  <TITLE>{title}</TITLE> 
  <ORG>
    <ORGUNIT>{departmentNumber}</ORGUNIT>
  </ORG>
</vCard>]]></vcard-mapping> 
    <nameField>cn</nameField> 
    <emailField>mail</emailField> 
    <groupNameField>cn</groupNameField> 
    <groupMemberField>member</groupMemberField> 
    <groupDescriptionField>description</groupDescriptionField> 
    <posixMode>false</posixMode>
  </ldap> 
  <provider>
    <vcard>
      <className>org.jivesoftware.wildfire.ldap.LdapVCardProvider</className>
    </vcard> 
    <user>
      <className>org.jivesoftware.wildfire.ldap.LdapUserProvider</className>
    </user> 
    <auth>
      <className>org.jivesoftware.wildfire.ldap.LdapAuthProvider</className>
    </auth> 
    <group>
      <className>org.jivesoftware.wildfire.ldap.LdapGroupProvider</className>
    </group>
  </provider> 
  <setup>true</setup>
</jive>

