Virtual server setup

[Alan DeKok]

Vincent Rusilowicz wrote:
> I have reloaded the server and started from scratch again.  I was able
> to authenticate with the default config, when adding client and user
> info.  In my effort to try and convert each client to use a separate
> virtual so separate user files

  You still haven't explained *why* you need that.  You're focusing on a
solution.  Instead, talk about the problem.  Maybe there's another
solution which is better.

> can be used I am not able to
> authenticate.  I see the auth attempt match an entry in my second_users
> file, but I get a WARNING message.

  Yes, because you butchered the configuration, and broke it.  You
deleted the "pap" module from the "authenticate" section.

  Why?  Just... why?  What possible benefit is there from destroying the
"authenticate" section?

  If you *do* want "users" files which are unique per client, there are
a few ways to do it.  The choice of solutions can depend on how many
clients you have.

  One way may be this:

- create multiple instances of the "files" module, one for each client.

- name them after the clients, so that you can keep track of which
module matches which client.  i.e. name them after the client IP
address, for simplicity.  i.e.

	files files_192.168.1.2 {
		...
	}

- select them dynamically at run-time via a "switch" statement.

- i.e. remove the "files" reference from "authorize", and replace it
with a switch:

	switch "%{Client-IP-Address}" {
		case {
			files
		}

		case 192.168.1.2 {
			files_192.168.1.2
		}

		...
	}

  And don't change *anything* else.  Butchering random things in the
configuration files is a guaranteed way to break the server.

  Alan DeKok.