Details
-
New Feature
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
2.0.0-M5
-
None
-
None
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.