This is the discussion I have been having with Amember. I thought I would share it with everyone here. MY QUESTION: Can amember be installed on a DOMAIN -- OTHER THAN THE DOMAIN -- where vbulletin is installed (both domains on the same server). For example: Vbulletin is on MAINDOMAIN.com/forums/ Can amember be put on NEWDOMAIN.com .... and still provide access control to the vipadulttravel.com/forums/??? THE ANSWER CONFUSED ME SO I RE-ASKED: The vbulletin is operating on the MAINDOMAIN.com. There is only ONE database as far as I can tell with the example I am giving you. I want amember on another domain (EMPTY) that is "generic" in name. There is nothing on this domain but amember. This amember would need to take care of the MAINDOMAIN.com member management. ---------------------- QUESTION TO USERS HERE: Has/Is anyone using Amember to control access to protected content ACROSS multiple directories (domains) on the same server? More specifically, can amember control password access to directories OUTSIDE of the path where amember is located -- but on the same server.
1. Yes, it is possible to use vBulletin integration without any problems (however, single-login will not work, because there are different domains). 2. It is often possible (depends on your server settings) to protect files on other domains located on the same servers using htpasswd password protection (with popup login box, etc) 3. It is impossible to use advanced protection techniques (new_rewrite, php_include) across domains, because cookies can be set for one domain only.
I am working on a specific project so I am attempting to clarify my understanding of whether this will work under amember script. ASSUMING the following ... 1. Amember installed on one domain/directory on a machine. (For example, amember is installed on domain ANIMALS.COM) 2. One or more domains/directories on the same machine need access (and authorization) control from amember's database. (For example, DOGS.COM has a /members/ directory that needs authorization data from the amember which is located on ANIMALS domain) SO: When a person attempts to enter DOGS.COM/members/, a plain htpassword box will pop up, ... and provided the user enters a valid user/pass, the user will obtain access to the member directory on the domain chosen (in this example, DOGS.COM/members/). SO the user DOES NOT need to go through AMEMBER for access -- even though the ORIGINAL sign-up occurred through AMEMBER. At this point of entering a secured area (on dogs.com), Amember is still in the background and the client doesn't need to enter through amember script (located on animals.com). QUESTION: AM I CORRECT in my understanding of how cross-directory password/authorization can work with this SPECIFIC example?