[
https://issues.apache.org/jira/browse/ISIS-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1503:
------------------------------
Description:
... to provide the ability to run fixture scripts that use the wrapper factory
from contexts where there is no current user, in particular during
UserRegistration.
The AuthenticationSessionProvider (internal) service should also report the
current user/roles (as well as UserService)
was:
Currently fixtures are run using the "initialisation" dummy account. Although
this can be explicitly overridden using the SudoService, it results in a lot of
boilerplate.
It would be nice instead if the fixture script framework (either FixtureScripts
service, or ExecutionContext, or FixtureScript class) could specify the user
account to use, ie call SudoService for us.
Summary: Allow security checking be disabled when running via
SudoService. (was: The FixtureScripts service ought to provide an easier
mechanism to specify which user account to run the fixtures as. )
> Allow security checking be disabled when running via SudoService.
> -----------------------------------------------------------------
>
> Key: ISIS-1503
> URL: https://issues.apache.org/jira/browse/ISIS-1503
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.13.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: 1.13.2
>
>
> ... to provide the ability to run fixture scripts that use the wrapper
> factory from contexts where there is no current user, in particular during
> UserRegistration.
> The AuthenticationSessionProvider (internal) service should also report the
> current user/roles (as well as UserService)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
