Hi Rico, what's the order of your server/security/userManagers nodes? Would you check it for all your related instances that are in sync? Afaik there are two conditions: External (LDAP accounts) should be ordered after system (f.e. superuser) and before admin (common Magnolia users) at once which prevents you from authentication failures during de/activation. Then public (PUR accounts in case you're using this Magnolia feature) should be located before external to take the public accounts during PUR authentication rather than externals when you authenticate with "not core" user when UserManager is used if it's needed to get the current/other user objects. Hope this is the source of your issue.
-- Best regards, Zdenek Skodik Magnolia International Ltd. Magnolia® - Simple Open-Source Content Management On Fri, 2010-02-26 at 15:35 +0100, Rico Jansen wrote: > > I am running tests with activation in our test environment, and I am > running into issues > when activating and deactivating pages when being logged in as a LDAP > user. > Activation fails with a 401 authorisation failed message even though > both instances > are configured to use LDAP,strangely enough deactivation does work. > I suspect that activation does not work because there is no user > password > associated with an external user. Why deactivation does work I don't > know. > > For now I have changed our workflow xml to use an physical user in > the > repository to activate the pages. This works for now, although > auditing > changes becomes difficult due to fact that all activations are > registered > under the same user. > > I hope there is a better solution to this issue. > > Regards, > -- > Rico Jansen ([email protected]) > "You call it untidy, I call it LRU ordered" -- Daniel Barlow > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
