OK --- so I have a fairly complex issue here which I need resolved.

Server: Apache running Plesk 7.5

We are currently developing an online application which basically will
give customers the ability to create an account. Once their account is
created they have the ability to select the domain from which they
want to access the account. Basically - their own personal login page.

First off the customer will be able to select their own "name"
(without spaces or special characters).
Second they wll be able to select the domain from which this account
can be accessed. In other words we will have a list of about 5 domain
names that we registered which the customer will have the ability to
select form.

Once he enters his name and select the domain name from the list and
saves the results his personal login page will be.

http://name.domain.com

Currently we have the system setup so his account mod_rewrites to
http://www.domain.com/name (from a long php string) and the login page
works fine.

We just can't seems to get it to work so the sub domains are automatically created.

All this has to happen automatcally meaning that we can't be manually
going into plesk to add a subdomain each time a client creates an
account. And also, the customer will be able to change the "name" and
select a different subdomain at any time (meaning the previous
name/subdoman will of course not work anymore once he saves the info).

I believe this should all be possible via mod_rewrite but we are
lookng for the least complex solution which also creates the LEAST
amount of system load.

Ok... so thats one issue.

Next --- what we are trying to do is give that customer the ability to
add his own domain name or subdomain to the system. Basically lets say
the customer has the domain "mydomain.com" and he wants that all his
internal employees or customers go to "subdomain.mydomain.com" to
acccess the login page... in effect creating a total private labled
system where the URL always appears to be his subdomain...

Regardng this issue I was thinking that if the first problem was
solved, meanng that "name.domain.com" actually works then we could
just tell the client to have his host create a cname record to point
any subdomain he chooses to cname to (in this case) "name.domain.com".

If my logic is correct then as long as all links on the
name.domain.com side (our system) are relative then as the customer
logs in and browses through the site the pages should all work will
the domain name url in the browser window will always show
"subdomain.mydomain.com" along with any other files/folders on our
system?

OK... so thats the second issue.

Now assuming there is a soluton to that problem here comes the next
one... lets assume that customer wants to have the
"subdomain.mydomain.com" ssl protected... meaning that he can go to
https://subdomain.mydomain.com (notce the "S" in https)... if his web
hosting account were setup wth his own ssl certifcate for
subdomain.mydomain.com would the customer still be able to access all
the pages from the main system while the URLs will all stay the same
just like the http version without any security warnings. If no, what
could be done to ensure this does work.

OK... final problem

Now assuming THAT above situation is solved... lets assume that in
order to access name.domain.com we want that to be secure meaning you
have to go to https://name.subdomain.com and we have a wildcare ssl
certificate or something to enable this. Now, lets assume the customer
again wants to only have the login page as
https://subdomain.mydomain.com but all data is coming via cname from
https://name.domain.com  would his server be able to authenticate this
someone in a secure fashion to ensure the communicate from the client
side to https://subdoman.mydomain.com is secure while the
communication from https://subdomain.mydomain.com to
https://name.domain.com is secure.

God... I really hope I don't have anyone pullng out there hair at this point.

Please excuse my lack of being able to explain these problems
correctly. Feel free to ask any follow up questions and I greatly
appreciate as much help as possible to get this resolved as its very
important.

I need solutions to all issues so I can get all issues above resolved
and working on Plesk 7.5 without manually creating anything.

Chris