diff options
Diffstat (limited to 'docs/html/win32.html')
| -rw-r--r-- | docs/html/win32.html | 231 |
1 files changed, 211 insertions, 20 deletions
diff --git a/docs/html/win32.html b/docs/html/win32.html index 32f2515e8..6b639622d 100644 --- a/docs/html/win32.html +++ b/docs/html/win32.html @@ -301,7 +301,7 @@ CLASS="COMMAND" ><DIV CLASS="EXAMPLE" ><A -NAME="AEN1012" +NAME="AEN1038" ></A ><P ><B @@ -1130,7 +1130,9 @@ TARGET="_top" ></LI ><LI ><P -> Modify the invocation of all system() calls in all perl scripts in your Bugzilla directory. For instance, change this line in processmail: +> Modify the invocation of all system() calls in all perl + scripts in your Bugzilla directory. For instance, change + this line in processmail: <TABLE BORDER="0" BGCOLOR="#E0E0E0" @@ -1141,14 +1143,14 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" ->system ("./processmail.pl",@ARGLIST); +> +system ("./processmail.pl",@ARGLIST); </PRE ></FONT ></TD ></TR ></TABLE -> -to +> to <TABLE BORDER="0" BGCOLOR="#E0E0E0" @@ -1159,7 +1161,8 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" ->system ("perl processmail.pl",@ARGLIST); +> +system ("perl processmail.pl",@ARGLIST); </PRE ></FONT ></TD @@ -1168,6 +1171,94 @@ CLASS="PROGRAMLISTING" > </P ></LI +><LI +><P +> Add <TT +CLASS="FUNCTION" +>binmode()</TT +> calls so attachments + will work (<A +HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000" +TARGET="_top" +>bug 62000</A +>). + </P +><P +> Because Microsoft Windows based systems handle binary + files different than Unix based systems, you need to add + the following lines to + <TT +CLASS="FILENAME" +>createattachment.cgi</TT +> and + <TT +CLASS="FILENAME" +>showattachment.cgi</TT +> before the + <TT +CLASS="FUNCTION" +>require 'CGI.pl';</TT +> line.</P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>binmode(STDIN); +binmode(STDOUT);</PRE +></FONT +></TD +></TR +></TABLE +> + </P +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +> According to <A +HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000" +TARGET="_top" +>bug 62000</A +>, the perl documentation says that you should always use <TT +CLASS="FUNCTION" +>binmode()</TT +> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <TT +CLASS="FUNCTION" +>binmode()</TT +> at the begining of the attachment files, there should be logic to determine if <TT +CLASS="FUNCTION" +>binmode()</TT +> is needed or not. + </P +></TD +></TR +></TABLE +></DIV +></LI ></OL ></DIV ><DIV @@ -1195,7 +1286,9 @@ VALIGN="TOP" relationships to Properties -> Home directory (tab) -> Application Settings (section) -> Configuration (button), such as: - <TABLE + </P +><P +> <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -1254,7 +1347,7 @@ VALIGN="TOP" ><P > From Andrew Pearson: <A -NAME="AEN1169" +NAME="AEN1212" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" @@ -1272,7 +1365,23 @@ TARGET="_top" registry at the following location: </P ><P -> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap +> <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap + </PRE +></FONT +></TD +></TR +></TABLE +> </P ><P > The keys should be called ".pl" and ".cgi", and both @@ -1319,11 +1428,12 @@ VALIGN="TOP" <EM >not necessary</EM > for Bugzilla 2.13 and - later. + later, which includes the current release, Bugzilla + 2.14. <DIV CLASS="EXAMPLE" ><A -NAME="AEN1180" +NAME="AEN1224" ></A ><P ><B @@ -1331,7 +1441,7 @@ NAME="AEN1180" 2.12 or earlier</B ></P ><P -> Replace this: +> Replace this: <TABLE BORDER="0" BGCOLOR="#E0E0E0" @@ -1342,16 +1452,16 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" -> -SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SqlQuote(substr($realcryptpwd, 0, 2)) . ")"); -my $enteredcryptpwd = FetchOneColumn(); +> +SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")"); +my $enteredcryptpwd = FetchOneColumn(); </PRE ></FONT ></TD ></TR ></TABLE -> - with this: +> +with this: <TABLE BORDER="0" BGCOLOR="#E0E0E0" @@ -1362,14 +1472,14 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" -> -my $enteredcryptpwd = $enteredpwd +> +my $enteredcryptpwd = $enteredpwd </PRE ></FONT ></TD ></TR ></TABLE -> +> in cgi.pl. </P ></DIV @@ -1380,6 +1490,87 @@ my $enteredcryptpwd = $enteredpwd ></TABLE ></DIV ></DIV +><DIV +CLASS="SECTION" +><H2 +CLASS="SECTION" +><A +NAME="BZLDAP" +>3.6.3. Bugzilla LDAP Integration</A +></H2 +><P +> What follows is some late-breaking information on using the + LDAP authentication options with Bugzilla. The author has not + tested these (nor even formatted this section!) so please + contribute feedback to the newsgroup. + </P +><P +CLASS="LITERALLAYOUT" +>Mozilla::LDAP module<br> +<br> +The Mozilla::LDAP module allows you to use LDAP for authentication to<br> +the Bugzilla system. This module is not required if you are not using<br> +LDAP.<br> +<br> +Mozilla::LDAP (aka PerLDAP) is available for download from<br> +http://www.mozilla.org/directory.<br> +<br> +NOTE: The Mozilla::LDAP module requires Netscape's Directory SDK.<br> +Follow the link for "Directory SDK for C" on that same page to<br> +download the SDK first. After you have installed this SDK, then<br> +install the PerLDAP module.<br> +----------------------------------------------------------------------<br> +<br> +Post-Installation Checklist<br> +----------------------------------------------------------------------<br> +Set useLDAP to "On" **only** if you will be using an LDAP directory<br> +for authentication. Be very careful when setting up this parameter;<br> +if you set LDAP authentication, but do not have a valid LDAP directory<br> +set up, you will not be able to log back in to Bugzilla once you log<br> +out. (If this happens, you can get back in by manually editing the<br> +data/params file, and setting useLDAP back to 0.)<br> +<br> +If using LDAP, you must set the three additional parameters:<br> +<br> +Set LDAPserver to the name (and optionally port) of your LDAP server.<br> +If no port is specified, it defaults to the default port of 389. (e.g<br> +"ldap.mycompany.com" or "ldap.mycompany.com:1234")<br> +<br> +Set LDAPBaseDN to the base DN for searching for users in your LDAP<br> +directory. (e.g. "ou=People,o=MyCompany") uids must be unique under<br> +the DN specified here.<br> +<br> +Set LDAPmailattribute to the name of the attribute in your LDAP<br> +directory which contains the primary email address. On most directory<br> +servers available, this is "mail", but you may need to change this.<br> +----------------------------------------------------------------------<br> +<br> +(Not sure where this bit should go, but it's important that it be in<br> +there somewhere...)<br> +----------------------------------------------------------------------<br> +Using LDAP authentication for Bugzilla:<br> +<br> +The existing authentication scheme for Bugzilla uses email addresses<br> +as the primary user ID, and a password to authenticate that user. All<br> +places within Bugzilla where you need to deal with user ID (e.g<br> +assigning a bug) use the email address.<br> +<br> +The LDAP authentication builds on top of this scheme, rather than<br> +replacing it. The initial log in is done with a username and password<br> +for the LDAP directory. This then fetches the email address from LDAP<br> +and authenticates seamlessly in the standard Bugzilla authentication<br> +scheme using this email address. If an account for this address<br> +already exists in your Bugzilla system, it will log in to that<br> +account. If no account for that email address exists, one is created<br> +at the time of login. (In this case, Bugzilla will attempt to use the<br> +"displayName" or "cn" attribute to determine the user's full name.)<br> +<br> +After authentication, all other user-related tasks are still handled<br> +by email address, not LDAP username. You still assign bugs by email<br> +address, query on users by email address, etc.<br> +----------------------------------------------------------------------<br> + </P +></DIV ></DIV ><DIV CLASS="NAVFOOTER" |