You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@isis.apache.org by "Daniel Keir Haywood (Jira)" <ji...@apache.org> on 2021/08/05 22:50:00 UTC

[jira] [Resolved] (ISIS-2728) Extend UserMemento to contain application tenancy path, and callback to allow secman etc to populate.

     [ https://issues.apache.org/jira/browse/ISIS-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Keir Haywood resolved ISIS-2728.
---------------------------------------
    Resolution: Fixed

> 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)