params.xml 6.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
  3. "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
  4. <section id="auth_db.parameters" xmlns:xi="http://www.w3.org/2001/XInclude">
  5. <sectioninfo>
  6. </sectioninfo>
  7. <title>Parameters</title>
  8. <section id="auth_db.db_url">
  9. <title><varname>db_url</varname> (string)</title>
  10. <para>
  11. This is URL of the database to be used. Value of the parameter
  12. depends on the database module used. For example for mysql and
  13. postgres modules this is something like
  14. mysql://username:password@host:port/database. For dbtext module
  15. (which stores data in plaintext files) it is directory in which the
  16. database resides.
  17. </para>
  18. <para>
  19. Default value is "mysql://serro:47serro11@localhost/ser".
  20. </para>
  21. <example>
  22. <title><varname>db_url</varname> parameter usage</title>
  23. <programlisting>
  24. modparam("auth_db", "db_url", "mysql://foo:[email protected]/ser")
  25. </programlisting>
  26. </example>
  27. </section>
  28. <section id="user_column">
  29. <title><varname>user_column</varname> (string)</title>
  30. <para>
  31. This is the name of the column holding usernames. Default value is
  32. fine for most people. Use the parameter if you really need to
  33. change it.
  34. </para>
  35. <para>
  36. Default value is "username".
  37. </para>
  38. <example>
  39. <title><varname>user_column</varname> usage</title>
  40. <programlisting>
  41. modparam("auth_db", "user_column", "user")
  42. </programlisting>
  43. </example>
  44. </section>
  45. <section id="domain_column">
  46. <title><varname>domain_column</varname> (string)</title>
  47. <para>
  48. This is the name of the column holding domains of users. Default
  49. value is fine for most people. Use the parameter if you really need
  50. to change it.
  51. </para>
  52. <para>
  53. Default value is "domain".
  54. </para>
  55. <example>
  56. <title><varname>domain_column</varname> usage</title>
  57. <programlisting>
  58. modparam("auth_db", "domain_column", "domain")
  59. </programlisting>
  60. </example>
  61. </section>
  62. <section id="password_column">
  63. <title><varname>password_column</varname> (string)</title>
  64. <para>
  65. This is the name of the column holding passwords. Passwords can be
  66. either stored as plain text or pre-calculated HA1 strings. HA1
  67. strings are MD5 hashes of username, password, and realm. HA1
  68. strings are more safe because the server doesn't need to know
  69. plaintext passwords and they cannot be obtained from HA1 strings.
  70. </para>
  71. <para>
  72. Default value is "ha1".
  73. </para>
  74. <example>
  75. <title><varname>password_column</varname> usage</title>
  76. <programlisting>
  77. modparam("auth_db", "password_column", "password")
  78. </programlisting>
  79. </example>
  80. </section>
  81. <section id="rpid_column">
  82. <title><varname>rpid_column</varname> (string)</title>
  83. <para>
  84. This is the name of the column holding information for the
  85. Remote-Party-ID header field. Default value is fine for most
  86. people. Use the parameter if you really need to change it.
  87. </para>
  88. <para>
  89. Default value is "rpid".
  90. </para>
  91. <example>
  92. <title><varname>rpid_column</varname> usage</title>
  93. <programlisting>
  94. modparam("auth_db", "rpid_column", "remote_party_id")
  95. </programlisting>
  96. </example>
  97. </section>
  98. <section id="calculate_ha1">
  99. <title><varname>calculate_ha1</varname> (integer)</title>
  100. <para>
  101. This parameter tells server whether it should read plaintext
  102. password from the database or HA1 string. If the parameter is set to
  103. 1 then the server will assume that the column pointed to by
  104. <varname>plain_password_column</varname> contains plaintext passwords and
  105. it will calculate HA1 strings on the fly.
  106. </para>
  107. <para>
  108. If the parameter is set to 0 then the server assumes that the
  109. database contains HA1 strings directly and will not calculate
  110. them. In this case it will use value of <varname>password_column</varname>
  111. as name of column with HA1 password.
  112. If username parameter of credentials contains also @domain
  113. (some user agents put domain in username parameter), then column
  114. pointed to by <varname>password_column_2</varname> parameter will
  115. be used instead. This column should also contain HA1 strings but
  116. they should be calculated including the domain in the username
  117. parameter (as opposed to <varname>password_column</varname> which
  118. (when containing HA1 strings) should always contains HA1 strings
  119. calculated without domain in username.
  120. </para>
  121. <para>
  122. This ensures that the authentication will always work when using
  123. pre-calculated HA1 string, not depending on the presence of the
  124. domain in username.
  125. </para>
  126. <para>
  127. Default value of this parameter is 0.
  128. </para>
  129. <example>
  130. <title><varname>calculate_ha1</varname>usage</title>
  131. <programlisting>
  132. modparam("auth_db", "calculate_ha1", 1)
  133. </programlisting>
  134. </example>
  135. </section>
  136. <section id="plain_password_column">
  137. <title><varname>plain_password_column</varname> (string)</title>
  138. <para>
  139. This parameter holds the name of column holding plain text password.
  140. This column is used when calculate_ha1 is set.
  141. </para>
  142. <para>
  143. Default value is "password".
  144. </para>
  145. <example>
  146. <title><varname>plain_password_column</varname> usage</title>
  147. <programlisting>
  148. modparam("auth_db", "plain_password_column", "password")
  149. </programlisting>
  150. </example>
  151. </section>
  152. <section id="password_column_2">
  153. <title><varname>password_column_2</varname> (string)</title>
  154. <para>
  155. As described in the previous section this parameter contains name
  156. of column holding pre-calculated HA1 string that were calculated
  157. including the domain in the username. This parameter is used only
  158. when <varname>calculate_ha1</varname> is set to 0 and user agent
  159. send a credentials containing the domain in the username.
  160. </para>
  161. <para>
  162. Default value of the parameter is ha1b.
  163. </para>
  164. <example>
  165. <title><varname>password_column_2</varname> usage</title>
  166. <programlisting>
  167. modparam("auth_db", "password_column_2", "ha1_2")
  168. </programlisting>
  169. </example>
  170. </section>
  171. <section id="use_rpid">
  172. <title><varname>use_rpid</varname> (integer)</title>
  173. <para>
  174. This parameter specifies whether the server should fetch a value
  175. for the Remote-Party-ID header field from the database.
  176. </para>
  177. <para>
  178. If the parameter is set to 1 the server expects to find a value for
  179. this header in the column specified by the
  180. <varname>rpid_column</varname> parameter.
  181. </para>
  182. <para>
  183. Default value of this parameter is 0.
  184. </para>
  185. <example>
  186. <title><varname>use_rpid</varname>usage</title>
  187. <programlisting>
  188. modparam("auth_db", "use_rpid", 1)
  189. </programlisting>
  190. </example>
  191. </section>
  192. </section>