[ http://jira.magnolia.info/browse/MAGNOLIA-1402?page=comments#action_13692 ] Philipp Bracher commented on MAGNOLIA-1402: -------------------------------------------
not sure if this is the right fix. The original intention was that what ever solution you use (JAAS, custom, ...) you provide a UserManager providing user objects (language, ... settings). This can be used in other places > Context.getLocale() always tries to load a user from userManager (jcr) also > in case of an external jaas user > ------------------------------------------------------------------------------------------------------------ > > Key: MAGNOLIA-1402 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1402 > Project: Magnolia > Issue Type: Bug > Components: core > Affects Versions: 3.0.1 > Reporter: Fabrizio Giustina > Assigned To: Fabrizio Giustina > Priority: Minor > Fix For: 3.1 > > > When a user has been authenticated by jaas but it's not registered in > magnolia repository MgnlContext.getLocale() will always try to load it from > userManager. > The result is a couple of error/warning log at each request. This is not > needed since the context already knows if the user is a magnolia user. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
