You may find tomcat's request dumper valve useful in seeing what's
happening between the two instances. Add this to your server.xml :
<Valve classname="org.apache.catalina.valves.RequestDumperValve" />
inside the Host element
Warning: this valve set's the parameter decoding to the platform's
default character encoding. Use sparingly to diagnose request
header/parameter problems.
--David
Christian P. Praher wrote:
Hi David,
yes we can and we know that these two values need to be in sync.
The strange thing with this is as I said, that everything worked fine with
our 2.1rc3 installation and we have exported (part of) the config-tree and
user-tree to XML and imported it in 2.1.5, so that's why we don't understand
why it isn't working anymore.
Best regards,
chris
-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[EMAIL PROTECTED]
Gesendet: Samstag, 16. September 2006 20:21
An: [email protected]
Betreff: Re: [magnolia-user] Can't activate since migration from 2.1rc3 to
2.1.5
Question: Can you log in the adminCentral on both author and public with
the same credentials? User and password info on both have to be in sync
for the user activating content.
-David
Christian Praher wrote:
hi boris,
thanks for your quick response, see below.
-------- Original-Nachricht --------
Datum: Sat, 16 Sep 2006 16:23:20 +0200
Von: "Boris Kraft" <[email protected]>
An: [email protected]
Betreff: Re: [magnolia-user] Can\'t activate since migration from 2.1rc3
to 2.1.5
Is there a firewall between your instances? There is an activation
log, what does it say?
nope. The two instances in fact run on the same tomcat instance.
The problem is more related to user authentication.
As far as we understand the activation protocol everything is done inside
the SimpleExchangeServlet (what a name :-)). So the Activating party sends a
HTTP request to the SimpleExchangeServlet on the Activatee. THe request is
handled by the doGet (we see the debug output).
But before it would be dispatched to the activate(HttpServletRequest)
method, it fails due to Authenticator.authenticate returns false for the
request.
According to some further investigation the setActivationHeaders
apparaently does not set the "Authorization" credentials header on the
Activator side, or the activatee fails to retrieve them. This is the case
why the authenticate method exits prematurely
On the other side a "browser login" works out of the box, on both the
activating/activatee adminCentral.
So we are a bit clueless, since it worked very well with our 2.1rc3
version. Maybe there is an issue with regard to Activation, which we have
not defined (a flag in the config repository. the subscriber nodes are
configured well).
btw: do you guys know a decent module for tcpdump to easily get the http
headers and request details? What are you using to dump/intercept HTTP
traffic?
thanks for the pointers
-- Chris
--
David Smith
Network Operations Supervisor
Department of Entomology
Cornell University
2132 Comstock Hall
Ithaca, NY 14853
Phone: (607) 255-9571
Fax: (607) 255-0940
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
