.htaccess
 

is there a way to use 2 password files with .htaccess's Basic Authentication ?

I don't know of a way of doing it. What is the reason for using two password files?

There is a way to do it fairly simply if the 2 files are on the same server. ICQ me if you need it done. 20090489

Dont believe the standard mod_auth allows you to use two different files and merg them together, but there is a mod_auth that allows multiple htpasswd files to be used, you declare each on a separate line. Dont recall if it was an entirely freeware module or not, just remember installing it on some servers.

How do some web sites use multiple processors ? i mean, don't they use seperate password files for each processor?

If i were to use ibill and epoch at the same time, and added users of ibill to the same .htpasswd file, wouldnt that cause problems? esp since ibill does not automatically remove usernames..

i want to use seperate password file for ibill subscribers so i can easily track them to see which one is active which one is cancelled, while the epoch one is smoothly working on its own.


:helpme

No, they write to the same file thru their respective cgi script.

You can setup a simple cron job to merge x amount of files in to 1 password file

*/5 * * * * cat /path/to/.htpasswd1 /path/to/.htpasswd2 > /path/to/.newhtpasswd

That will merge .htpasswd1 and .htpasswd2 to .newhtpasswd every 5 minutes.

Nope, you don't know the countless hours I've spent trying this and there is just no way!

I've tried mod_rewrite along with mod_auth and nothing has EVER worked, don't waste your time, it's not worth it!

jDoG

They use the same password file. I haven't had problems with using multiple processors with one password file (4 different processors). iBill should remove usernames when the expire.

You could modify the cgi scripts that epoch and ibill gave you so that a username is added into it's own file and then merges the ibill and epoch file togather for the members area. That way ibill and epoch will have it's own file for you to keep track of, but there will be one file for your members area to look at. There is a problem in that if the same username gets added to both files and then they are merged togather. One of your members won't be able to get access. Both epoch and ibill should check the password file to see if there is already a username before adding it.

short and simple, multiple processors=same password file but custom cgis writing to password file for each company.

I know some of you guys already resolved this but I want to make it sound simple as possible.