![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 653325f)
raw | patch | inline | side by side (parent: 653325f)
| author | hickert <hickert@594d385d-05f5-0310-b6e9-bd551577e9d8> | |
| Wed, 15 Jun 2005 09:17:43 +0000 (09:17 +0000) | ||
| committer | hickert <hickert@594d385d-05f5-0310-b6e9-bd551577e9d8> | |
| Wed, 15 Jun 2005 09:17:43 +0000 (09:17 +0000) |
index bbaa7ab49b9297042211ffa892abc716f3ef1c32..dfc95bcf952b620c0ce10151f8fb114d0a2c8c5e 100644 (file)
+<body style='background-color:#A0A0A0;background-image:none'>
<form action="setup.php?check_globals=42" method="post" enctype="multipart/form-data">
<script language="JavaScript" type="text/javascript">
//-->
</script>
+{$errors}
+
<table cellspacing=0 cellpadding=0 style="width:100%;height:100%;">
<tr style="background-color:#CDF6C5">
<td style="border-bottom:1px solid black; height:50px;">
index 176b99e182927d606f6b27d811937d3af47b0809..ccd0b19bb5f671f10e53108a74c87c38da87675a 100644 (file)
<h1>{t}Setup finished{/t}</h1>
+{t}Basically the setup is finished. You can check the result of the schema check here and download the autogenerated gosa.conf below.{/t}
+
+<p class="seperator"> </p>
+
+<h2>{t}Schema Configuration{/t}</h2>
+<p>{$schemas}</p>
+
+<p class="seperator"> </p>
+
+<h2>{t}Configuration File{/t}</h2>
<p>
{t}GOsa setup has collected all data needed to create an initial configuration file. Save the the link below as your gosa.conf and place that file in /etc/gosa. Change it as needed.{/t}
</p>
-<p>
- > <b><a target='_new' href='setup.php?getconfig=1'>gosa.conf</a></b>
-</p>
+<input type='submit' name='getconf' value='{t}Download configuration{/t}'>
<p>
{t}After placing the file under /etc/gosa, place make sure that the webserver user is able to read gosa.conf, while other users shouldn't. You may want to execute these commands to achieve this requirement:{/t}
</p>
-<tt>
-# chown root.{$webgroup} /etc/gosa/gosa.conf<br>
+<pre>
+# chown root.{$webgroup} /etc/gosa/gosa.conf
# chmod 640 /etc/gosa/gosa.conf
-</tt>
-
-<div style="width:99%; text-align:right;">
- {if $mode ne 'ready'}
- <input type='submit' name='retry' value='{t}Retry{/t}'>
- {else}
- <input type='submit' name='login' value='{t}Sign in{/t}'>
- {/if}
-</div>
+</pre>
+
+<p class="plugbottom">
+ <input type="hidden" name="next" value="6">
+ <input type='submit' name='back' value='{t}Back{/t}'>
+ <input type='submit' name='retry' value='{t}Retry{/t}'>
+</p>
diff --git a/ihtml/themes/altlinux/setup_introduction.tpl b/ihtml/themes/altlinux/setup_introduction.tpl
index 526b1a5ebfad81c5a319036ccfb0d17a862635cc..4f8ada563e850c0c5d1917b1fff07652c2adcaa1 100644 (file)
<p>
{t}It looks like you're calling GOsa for the first time - no configuration was found. This setup like script will try to aid you in creating a working configuration by performing three major steps: first we'll check the PHP installation for required modules, than we're going to check for optional/needed programms and after you've provided basic informations for your LDAP connectivity, we're going to check your LDAP setup.{/t}
</p>
+<p class="seperator"> </p>
{$tests}
-<div style="width:99%; text-align:right;">
- <input type='submit' name='continue' value='{t}Continue{/t}' {$mode}>
-</div>
+<p class="plugbottom">
+ <input type="hidden" name="next" value="2">
+ <input type='submit' name='continue' value='{t}Continue{/t}'>
+</p>
<br>
<br>
index e75f6864fa91d2a573db47e06effa684e4b930a4..6d23e42efe2e85688544fbe3c855977f4ac7adbc 100644 (file)
<p>
{t}Step two looks for a set of helper programms and checks if they have the correct minimum version.{/t}
</p>
+<p class="seperator"> </p>
{$tests}
-{if $mode ne "disabled"}
-<p>
- <b>{t}We've inspected the webserver side now. Your setup seems to fit GOsa's needs. Lets go for the GOsa configuration part now...{/t}</b>
+<p class="plugbottom">
+ <input type="hidden" name="next" value="3">
+ <input type='submit' name='back' value='{t}Back{/t}'>
+ <input type='submit' name='continue2' value='{t}Continue{/t}'>
</p>
-{/if}
-
-<div style="width:99%; text-align:right;">
- <input type='submit' name='continue2' value='{t}Continue{/t}' {$mode}>
-</div>
index e1debc83a55910aa2e0a09eab183e0816599182e..68214b45ec729bad33a0f9e01142f15401422962 100644 (file)
{t}Now we're going include your LDAP server and create an initial configuration. After you've entered the server URI below, a quick check is performed if required LDAP schemas are in place. Samba versions are autodetected by the installed objectclasses. Details on how your LDAP tree is organized will be asked later on.{/t}
</p>
-<b>{t}Please enter the server URI{/t}</b>
+<p class="seperator"> </p>
<br>
-<input type='text' name='uri' maxlength='80' size='40' value='{$uri}'>
-<div style="width:99%; text-align:right;">
- <input type='submit' name='continue3' value='{t}Continue{/t}' {$mode}>
-</div>
+{t}Please enter the server URI to allow the setup to connect your LDAP server <i>(Example: ldap://your.server:389).</i>{/t}
+<br>
+<br>
+URI <input type='text' name='uri' maxlength='80' size='40' value='{$uri}'>
+
+<p class="plugbottom">
+ <input type="hidden" name="next" value="4">
+ <input type='submit' name='back' value='{t}Back{/t}'>
+ <input type='submit' name='continue3' value='{t}Continue{/t}'>
+</p>
index 57e2d896ee4fc339e3671bf66bd502635256d4a2..f19acf1763a2d61172dc7ca80d80096cf695887c 100644 (file)
<h1>{t}Setup continued...{/t}</h1>
+{t}The following fields allow the basic configuration of GOsa's behaviour and affect various properties in your main configuration.{/t}
+
+<p class="seperator"> </p>
<p>
{t}Enter a description for the location you're configuring here{/t}:
</p>
<table>
<tr>
- <td><b>{t}Location name{/t}</b></td>
+ <td>{t}Location name{/t}</td>
<td><input type='text' name='location' maxlength='80' size='25' value='{$location}'></td>
</tr>
</table>
+<p class="seperator"> </p>
<p>
- {t}Finally, you need to specify parameters to access the LDAP server. GOsa always acts as admin and manages access rights internally. This is a workaround till OpenLDAP's in directory ACI's are fully implemented. For this to work, we need the admin DN and the corresponding password.{/t}
+ {t}GOsa always acts as admin and manages access rights internally. This is a workaround till OpenLDAP's in directory ACI's are fully implemented. For this to work, we need the admin DN and the corresponding password.{/t}
</p>
<table>
<tr>
- <td><b>{t}Admin DN{/t}</b></td>
+ <td>{t}Admin DN{/t}</td>
<td><input type='text' name='admin' maxlength='80' size='40' value='{$admin}'></td>
</tr>
<tr>
- <td><b>{t}Admin password{/t}</b></td>
+ <td>{t}Admin password{/t}</td>
<td><input type='password' name='password' maxlength='20' size='20' value='{$password}'></td>
</tr>
</table>
+<p class="seperator"> </p>
<p>
{t}Some basic LDAP parameters are tunable and affect the locations where GOsa saves people and groups, including the way accounts get created. Check the values below if the fit your needs.{/t}
<table>
<tr>
- <td><b>{t}People storage ou{/t}</b></td>
+ <td>{t}Base {/t}</td>
+ <td><input type='text' name='base' maxlength='80' size='40' value='{$base}'></td>
+ </tr>
+ <tr>
+ <td>{t}People storage ou{/t}</td>
<td><input type='text' name='peopleou' maxlength='40' size='20' value='{$peopleou}'></td>
</tr>
<tr>
- <td><b>{t}People dn attribute{/t}</b></td>
+ <td>{t}People dn attribute{/t}</td>
<td>
<select size="1" name="peopledn">
{html_options values=$peopledns output=$peopledns selected=$peopledn}
</td>
</tr>
<tr>
- <td><b>{t}Group storage ou{/t}</b></td>
+ <td>{t}Group storage ou{/t}</td>
<td><input type='text' name='groupou' maxlength='40' size='20' value='{$groupou}'></td>
</tr>
<tr>
- <td><b>{t}ID base for users/groups{/t}</b></td>
+ <td>{t}ID base for users/groups{/t}</td>
<td><input type='text' name='uidbase' maxlength='20' size='10' value='{$uidbase}'></td>
</tr>
</table>
-<div style="width:99%; text-align:right;">
- <input type='submit' name='check' value='{t}Check{/t}' {$mode}>
-</div>
+<p class="seperator"> </p>
+
+<p>
+ {t}GOsa supports several encryption types for your passwords. Normally this is adjustable via user templates, but you can specify a default method to be used here, too.{/t}
+</p>
+
+<table>
+ <tr>
+ <td>{t}Encryption algorithm{/t}</td>
+ <td>
+ <select name="arr_crypts" size="1" title="">
+ {html_options options=$arr_cryptkeys selected=$arr_crypts}
+ </select>
+ </tr>
+</table>
+
+<p class="seperator"> </p>
+
+<p>
+ {t}GOsa has modular support for several mail methods. These methods provide interfaces to users mailboxes and general handling for quotas. You can choose the dummy plugin to leave all your mail settings untouched.{/t}
+</p>
+
+<table>
+ <tr>
+ <td>{t}Mail method{/t}</td>
+ <td>
+ <select name="mail" size="1" title="">
+ <option name="mail" value="disabled">{t}disabled{/t}</option>
+ {html_options options=$mail_methods selected=$mail}
+ </select>
+ </tr>
+</table>
+
+<p class="plugbottom">
+ <input type="hidden" name="next" value="5">
+ <input type='submit' name='back' value='{t}Back{/t}'>
+ <input type='submit' name='check' value='{t}Check{/t}'>
+</p>