Introduction

The procedure for installing Knowledgebox software onto a Cachepilot that uses proxy authentication is largely the same as that used normally. However, where this is the case (i.e. anyone wishing to gain access to the internet needs a current username and password), additional steps need to be completed before attempting to run core_data_update_noassets and subsequently setting the Site ID.

Procedure

1. Creating a username and password

Open a web browser and connect to the Cachepilot by entering the IP address (e.g 192.168.1.1) in the address bar.
Login as admin;
Select User Accounts from the buttons on the left of this window;

Select Add user;

Create a new username (i.e. knowledgebox);
Create a password for this new username (i.e. kbox);
Re-enter the password;
Select Open group for group membership - this gives full, unrestricted rights to this user with regard to web access;
Click once on the OK button.

This username and password will need to be entered in the Modify Proxy Settings page of the Knowledgebox System Engineer interface (see 3. below).

2. Amending the /etc/passwd file

This file needs to be amended if the number of usernames entered on the Cachepilot exceeds 499. The reason for this is that the install nub for Knowledgebox uses the IDs 500 for sapdb and 501 for kb. If these IDs are allocated to existing users this will cause the relevant file permissions to be incorrectly set and Knowledgebox will not run.

To amend the file, connect to the Cachepilot either using Putty or WinSCP.
Login as Root;

Go to /etc/passwd and open the file for editing (in WinSCP, select the file, right click and choose Edit);

Scroll down to the entries for IDs 500 and 501. If they are allocated to existing users select and cut them from this position;
Scroll to the end of the file and paste these entries in;
Highlight the ID number of each and change to a new number based on the last entry in this file, for example if the last entry is 621, these IDs need to be changed to 622 and 623 respectively;
Scroll up until you find the entries for sapdb and kb;
Select and cut them from this position and scroll up to ID 499;
Paste the entries for sapdb and kb after ID 499 and then save the file.

For this editing to take effect Knowledgebox will need to be re-started, ideally by re-booting the Cachepilot.

Troubleshooting

If after re-boot the file permissions are still incorrect and are still showing the original username and not kb or sapdb, you will need to amend a second passwd file.

This may be passwd.org or even ftppasswd, both of which may be found in the /etc directory.
(It is advisable to take a moment to check if either of these or other passwd files are present when first editing /etc/passwd.)

The cause of this error is that, if there is a second file, both will need to be amended otherwise the changes in permissions created by the editing of /etc/passwd will not be implemented after re-boot.

After making this second change re-boot the Cachepilot to restart Knowledgebox.

3. Knowledgebox proxy settings

Before attempting to set the SiteID it is necessary to enter the proxy settings for the Knowledgebox by using the System Engineer interface.

The default proxy settings for an authenticating Cachepilot are:

Proxy Host: 127.0.0.1
Proxy Port:  8000

Proxy user and password are those created as explained in section 1, in this case
user: knowledgebox
Password: kbox

Once this has been set return to the Knowledgebox System Engineer interface and select System Checks to see if Talkback has been achieved.

Troubleshooting

If Talkback cannot be achieved it will be necessary to add the URL kbuken.pearsonbroadband.com to the relevant Cachepilot whitelist.

Open a web browser and connect to the Cachepilot as detailed earlier.
Login as admin,
Select Web from the buttons on the left of this window,

Select Site Lists,

Select corporate (whitelist) from the list of existing site lists,

Enter the following URL – kbuken.pearsonbroadband.com – in the site list box,
Click once on OK.

Return to the Knowledgebox System Engineer interface and select System Checks to confirm that Talkback has been achieved.