[pubcookie-dev] mods to relay
fox at cac.washington.edu
Fri Jun 25 13:43:53 PDT 2004
> Date: Fri, 25 Jun 2004 13:28:30 -0700 (PDT)
> From: Nathan Dors <dors at cac.washington.edu>
> To: Jim Fox <fox at cac.washington.edu>
> Cc: pubcookie-dev at u.washington.edu
> Subject: Re: [pubcookie-dev] mods to relay
> The relay also uses the login_host. Wouldn't the
> case where relay and login server are on the same
> server also require a new relay_login_host?
When they are on the same system the new variable,
relay_login_host, would have to be used for the relay.
> Also, although the relay will use the new variable
> and query string parameter, do you think these
> should be documented as the primary/recommended way
> to use them? I'm thinking yes, but the fallbacks
> would work well except in these unusual cases.
I'd say document the new way as standard. The old way
was just for compatibility.
> On Thu, 24 Jun 2004, Jim Fox wrote:
>> A few fixes were required of the relay code.
>> The relay will use a new configuration file variable,
>> relay_login_uri, to determine the uri of the real login server.
>> This allows a relay to operate on the same system as the
>> login server. If relay_login_uri is missing the relay will
>> fall back to the login_uri as before.
>> The relay will accept a domain parameter on its uri, to
>> use in place of the enterprise_domain variable from config.
>> This will allow a single relay to serve multiple domains.
>> For example, the server app.myuw.net might use this httpd.conf
>> PubCookieLogin https://app.myuw.net/PCRELAY/?domain=.myuw.net
>> In case of a missing domain argument the relay will fall back
>> to enterprise_domain.
>> The relay now uses as its uri whatever it was called with.
>> It no longer uses the relay_uri config variable.
>> pubcookie-dev mailing list
>> pubcookie-dev at u.washington.edu
More information about the pubcookie-dev