[ic] Separate SSL domain works for checkout and not Admin

[Web Administrator]

Kevin,

I did not have that set. One issue is the customer owns seven domains. I
added all seven in CookieDomain directives. No luck.

I did not mention this earlier but I have no errors in error.log or in the
SSL server's logs.

When referred to the error page the domain is changed back to the non-ssl
domain which works fine. And as stated the checkout portion works fine. It
is switched to https://secure.domain.com and credit card numbers are pgp
encrypted and sent without issue. Customer is redirected to the standard
receipt page. For some reason the Admin balks at the domain switch but the
checkout does not.

In addition the login functionality on the customer side does not work at
all.

All of this will go away if I change the secure site to
https://www.domain.com and allow the dialog to pop up stating the cert is
valid and from an authority but is for another domain.

-Eli
>>
>> I am having problems with the admin portal after changing SSL to a
>> different domain, www.domain.com changes to secure.domain.com.
>>
>> I am on Interchange 4.8.3 after a recent upgrade.
>>
>> The checkout portion works fine after adding DomainTail and IpHead to
>> interchange.cfg.
>>
>> After logging into the Admin portal the first page appears and the
>> address is https://secure.domain.com. Clicking on any link brings up a
>> "maybe you need to log in" message.
>>
>> This only occurs for one of two sites. The second site logs into
>> https://secure.anotherdomain.com and then switches to
>> http://www.anotherdomain.com for any links in the admin. All the
>> configs only show the obvious differences when the files are diff'd. I
>> must be missing a config somewhere.
>>
>> Strangly neither worked before starting this e-mail and searching for
>> the above "maybe you need to log in" message.
>>
>> Any help would be greatly appreciated.
>>
> Have you tried setting the CookieDomain directive to .domain.com in
> your first domain's catalog.cfg file and to .anotherdomain.com in your
> other domain's catalog.cfg file?  Note the leading dot in both cases.
>
>>From the configuration manual:
>
>    3.12. CookieDomain
>
>    Allows a domain to be set so that multiple servers can
>    handle traffic. For example, to use server addresses of
>    secure.yourdomain.com and www.yourdomain.com, set it to:
>
>    CookieDomain    .yourdomain.com
>
>    More than one domain can be set. It must have at least two
>    periods or browsers will ignore it.
>
> --
>   _/   _/  _/_/_/_/  _/    _/  _/_/_/  _/    _/
>  _/_/_/   _/_/      _/    _/    _/    _/_/  _/   K e v i n   W a l s h
> _/ _/    _/          _/ _/     _/    _/  _/_/    kevin@cursor.biz
> _/   _/  _/_/_/_/      _/    _/_/_/  _/    _/
>
> _______________________________________________
> interchange-users mailing list
> interchange-users@interchange.redhat.com
> http://interchange.redhat.com/mailman/listinfo/interchange-users


Web Administrator
iDifferNet, INC.
(317) 698-1193