Hi Simon, since we're using Firefox as our browser it can not be an IE issue. The subscriber-settings are also correct, since we were only updating our current repositories from 2.1rc3 to 2.1.5 and have exported all the important configuration-nodes (config, users, ...) and importated it in our new version, so nothing should have changed ... This is really kind of a weird problem and I hope that there's some config-setting or so to resolve it ...
Best regards, chris -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[EMAIL PROTECTED] Gesendet: Samstag, 16. September 2006 17:24 An: [email protected] Betreff: Re: [magnolia-user] Can't activate since migration from 2.1rc3 to 2.1.5 Hi Christian, This might sound obvious (appologies if it is), but have you set the subscriber config correctly on both instances (/subscribers/SubscriberConfig in AdminCentral)? This has caught me out a few times, especially as the 2 URLs in the config are formatted differently (1 with protocol and 1 without). My other thoughts are that I've sometimes seen issues with activation from certain client configs, probably to do with IE versions. Never found what the problem was, but closing all browser windows and retrying a few times normally resolved it - no idea why though :-) Hope that helps, Simon On 16/09/06, Christian Praher <[email protected]> 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 > -- > "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ... > Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail > > ---------------------------------------------------------------- > for list details see > http://www.magnolia.info/en/magnolia/developer.html > ---------------------------------------------------------------- > ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
