[CAUSEWAY-2824] Ensure ImpersonatedUserHolder can be accessed during initial fixtures

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.0.0-M6
• Component/s: Core, Viewer Wicket
• Assignee: Daniel Keir Haywood
• Reporter: Daniel Keir Haywood
• Created: 26/Jul/21 09:10
• Updated: 25/Aug/21 14:33
• Resolved: 26/Jul/21 12:06

Description

The ImpersonatedUserHolderForWicket implementation introduced for keycloak ticket recently is superfluous (the existing ImpersonatedUserHolderForHttpSession works fine, I believe) but in any case the UserService that iterates over all of the available should be fault-tolerant to any of the impl's throwing an exception.

This currently happens if a fixture script called during initialization uses secman which results in a call to obtain the current user... there is no Wicket session and so the fixture scripts fail to run.