Hi Jan, hi Everyone! I have now solved the problem we had with activation:
The cause was that the user in question did not have any password set. This is an exceptional situation, caused by the fact that we imported these specific users into the system via XML-Import... In the normal GUI, the missing password is hard to catch, since the password isn't displayed anywhere. Once I used a JCR Browser on the users repo, it became fairly clear what the problem was. Setting a password (and activating the changed user to public instance) got rid of the problem. Thanks a lot for your feedback, Jan, you helped me get back on the right track to finding the solution, when I was all geared up to blame the network & firewall team ;-) Regards from Vienna, Richard Von: [email protected] [mailto:[email protected]] Im Auftrag von Jan Haderka Gesendet: Mittwoch, 05. Jänner 2011 12:04 An: Magnolia User-List Betreff: Re: AW: [magnolia-user] Activation Problem - network access to public system Hmm, good question :) It's been long time since I looked at this piece of code .... Subscriber has a non mandatory property "authenticationMethod". If not set, the BASIC auth should be used. The allowed values (unless you write custom Syndicator implementation) are either "basic" or "form" HTH, Jan On Jan 5, 2011, at 11:30 AM, Unger, Richard wrote: Hi! Thanks for your reply, and for confirming that activation requires connectivity only from author server to public server. Our users are authenticated by Magnolia, but we are using a custom Login-Filter. As such, the authentication is not "external", I think. The users are stored as magnolia users, and have been activated to the public instance. All required roles have also been activated to the public instance. What is very confusing to me is that activation works when I test from office1, but not from office2. Access from the two sites differs only in terms of network connectivity, we use the same authentication mechanism for the author instance. So I guess I need to look into the users themselves? There must be something about the user settings that is preventing correct authentication on activation. May I ask, what type of authentication is used for the activation request? Does work via the BASIC or FORM based LoginHandlers? Thanks for your help! Regards from Vienna, Richard Unger Von: [email protected]<mailto:[email protected]> [mailto:[email protected]] Im Auftrag von Jan Haderka Gesendet: Dienstag, 04. Jänner 2011 20:24 An: Magnolia User-List Betreff: Re: [magnolia-user] Activation Problem - network access to public system Activation is issued from the author server to the public server. Client is not part of that process apart from triggering the request on the author instance. Is there any chance that you are using external user manager and SSO between author and public instances and in case of users logging in via SSO-proxy, their credentials are invalid for public? HTH, Jan On Jan 4, 2011, at 5:26 PM, Unger, Richard wrote: Happy New Year Magnolians! We have an urgent problem in production with the activation: >From our main office, users have direct network access to both public and >author instances, everything works. At a secondary office, users can access the authoring system only via a Single-Sign-On Proxy. Problem is that users at the secondary office cannot publish (see sample error message below). It seems that in order to activate, a client request to the public server is required. Is there any way to configure magnolia so that activation can take place entirely via the authoring system, i.e. without requiring network access from the client system to the public system? Thanks for your advice! Regards from Vienna, Richard Unger <image001.jpg> ________________________________ ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]<mailto:[email protected]>> ---------------------------------------------------------------- ________________________________ ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]<mailto:[email protected]>> ---------------------------------------------------------------- ________________________________ ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]<mailto:[email protected]>> ---------------------------------------------------------------- ________________________________ ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]<mailto:[email protected]>> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
