[MAGNOLIA-1402] Context.getLocale() always tries to load a user from userManager (jcr) also in case of an external jaas user Created: 25/Feb/07  Updated: 08/Mar/07  Resolved: 25/Feb/07

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.0.1
Fix Version/s: 3.1 M1

Type: Bug Priority: Minor
Reporter: Fabrizio Giustina Assignee: Fabrizio Giustina
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

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.



 Comments   
Comment by Fabrizio Giustina [ 25/Feb/07 ]

fixed in svn

Comment by Philipp Bracher [ 08/Mar/07 ]

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

Generated at Mon Feb 12 03:26:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.