[
https://issues.apache.org/jira/browse/ISIS-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394367#comment-17394367
]
ASF subversion and git services commented on ISIS-2728:
-------------------------------------------------------
Commit 4d23cc85002025958d40676793c3df66070f998c in isis's branch
refs/heads/ISIS-2728 from danhaywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=4d23cc8 ]
ISIS-2728: extends the ImpersonateMenuAdvisor SPI to also advise on the
multiTokenTenancy
(cherry picked from commit 53cb34831d0b1d6088a591cfbe052f311504ea71)
> 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)
