Hello again, I've made some intermittent progress over the last few weeks, but am still having problems. My custom external UM is getting called properly now, as expected. When a new user is created in the external database, it is wrapped as an ExternalUser for use within magnolia (as suggested here, http://forum.magnolia-cms.com/forum/thread.html?threadId=07c95ac9-de12-48c6-a353-997047b94e84). However, I am using the demo-project for testing and its dependency on the PUR module seems to be a problem as it seems to take over the whole user registration process. During user registration, I get a ClassCastException in the AbstractPURProcessor.updateContext() method where the user instance is expected to be of type MgnlUser.
As I can find no documentation on the internals of the user registration/login process or how it can be influenced besides custom userManagers/loginModules (obviously the PUR module is interfering at another point in the process), I would appreciate it if someone could roughly outline which components are involved, in which sequence, and how they are configured. Also, is it possible to use the demo-project with a custom external userManager, i.e. circumvent the PUR module altogether? If using the demo-project the wrong approach to testing altogether, could someone advise me on how to proceed from this point on? I have a custom ExternalUserManager which works on custom ExternalUser instances and would like to use these components for users on the public instance (analogous to the PUR module, but using an external database). Thanks, Rade -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=ab673447-5c87-40d6-981c-a45ca8f8cd2a ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
