[pubcookie-dev] PUBCOOKIE_LOGIN_CONFIG_FILE different virtual host

[Bradley Schwoerer]

Since we (Univ of Wisc-Madison) are guilty of programming this functionality
into pubcookie, I figure we should give an answer to this :).  We do have
three login CGI's configured using this functionality.

You need to do something like what is below in the virtual host for port
443.  On the port 80 virtual host we just redirect all traffic to port 443.

setenv PUBCOOKIE_LOGIN_CONFIG_FILE
/usr/local/webiso/pubcookie/config-weblogin


-Bradley




On 4/5/06 9:47 AM, "Steve Losen" <scl at sasha.acc.Virginia.EDU> wrote:

>> In this case, wich is the functionality of PUBCOOKIE_LOGIN_CONFIG_FILE's
>> environment variable....
>> 
>> In pubcookie's home I can read...
>> 
>> Run-Time Config File Setup
>> The login cgi and keyserver read configuration settings from a run-time
>> configuration file. The default location, PREFIX/config, is compiled in by
>> default.
>> The login cgi will use an alternate config file if a
>> PUBCOOKIE_LOGIN_CONFIG_FILE environment variable defines one. This is useful
>> when more than one logical login server is running on the same machine
>> (using virutal hosts in Apache).
>> 
>>  Do yo think is better to install multiples instances of pubccokie, one for
>> each kind of login in ldap???????????
>> 
> 
> I suppose you could have two virtual hosts on the login server, with
> two config files for the login CGI.  Then maybe you can have two virtual
> hosts on the application server configured to authenticate to different
> virtual hosts on the login server.
> 
> So yes, you would essentially set up two different pubcookie environments.
> 
> Steve Losen   scl at virginia.edu    phone: 434-924-0640
> 
> University of Virginia               ITC Unix Support
> 
> 
> _______________________________________________
> pubcookie-dev mailing list
> pubcookie-dev at u.washington.edu
> http://mailman1.u.washington.edu/mailman/listinfo/pubcookie-dev