[
https://issues.apache.org/jira/browse/ISIS-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Keir Haywood updated ISIS-2728:
--------------------------------------
Description:
The rationale for this is to allow a higher level of abstraction for domain
apps, so that any domain code would be able to simply use the framework's
generic _UserService_ rather than have to map across to the secman-specific
_ApplicationUserRepository_.
We can either store this directly as a field or within a (serializable) set of
attributes.
Storing as a field may be reasonable: this is a piece of info that could
reasonable be known for any securiyt implementation. One objection to using
attributes is that nominally UserMemento is an immutable value.
was:
The rationale for this is to allow a higher level of abstraction for domain
apps. For example, secman's _ApplicationUser_ entity has the notion of
"atPath" (application tenancy path), which coupled with
_ApplicationTenancyEvaluator_ allows for data tenancy, ie "ownership" of data.
If though _UserMemento_ was able to hold onto the atPath in some generic
fashion, then any domain code would be able to simply use the framework's
generic _UserService_ rather than have to map across to the secman-specific
_ApplicationUserRepository_.
> Extend UserMemento to contain application tenancy path, and callback to allow
> secman etc to populate.
> -----------------------------------------------------------------------------------------------------
>
> Key: ISIS-2728
> URL: https://issues.apache.org/jira/browse/ISIS-2728
> Project: Isis
> Issue Type: New Feature
> Affects Versions: 2.0.0-M5
> Reporter: Daniel Keir Haywood
> Assignee: Daniel Keir Haywood
> Priority: Minor
> Fix For: 2.0.0-M6
>
>
> The rationale for this is to allow a higher level of abstraction for domain
> apps, so that any domain code would be able to simply use the framework's
> generic _UserService_ rather than have to map across to the secman-specific
> _ApplicationUserRepository_.
> We can either store this directly as a field or within a (serializable) set
> of attributes.
> Storing as a field may be reasonable: this is a piece of info that could
> reasonable be known for any securiyt implementation. One objection to using
> attributes is that nominally UserMemento is an immutable value.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
