[
https://issues.apache.org/jira/browse/ISIS-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-999:
-----------------------------
Description:
A log showing the following info (at least) must be available:
* Account who has been logged.
* Date/Time the session has been started.
* Date/Time the session has been ended (by the user or automatically due to
inactivity, etc.).
This will probably require some sort of new optional service defined in the
applib, perhaps implemented by isisaddons' isis-module-security.
The implementation will probably also have to reach into Wicket internals in
order to obtain details of currently logged on users (assuming that information
is available).
If we do rely on Wicket, then there's a question about clustering.
was:
This will probably require some sort of new optional service defined in the
applib, perhaps implemented by isisaddons' isis-module-security.
The implementation will probably also have to reach into Wicket internals in
order to obtain details of currently logged on users (assuming that information
is available).
If we do rely on Wicket, then there's a question about clustering.
> Administrator should be able to view currently logged-in accounts and
> sessions info
> -----------------------------------------------------------------------------------
>
> Key: ISIS-999
> URL: https://issues.apache.org/jira/browse/ISIS-999
> Project: Isis
> Issue Type: New Feature
> Components: Core, Viewer: Wicket
> Affects Versions: viewer-wicket-1.7.0, core-1.7.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: viewer-wicket-1.9.0, core-1.9.0
>
>
> A log showing the following info (at least) must be available:
> * Account who has been logged.
> * Date/Time the session has been started.
> * Date/Time the session has been ended (by the user or automatically due to
> inactivity, etc.).
> This will probably require some sort of new optional service defined in the
> applib, perhaps implemented by isisaddons' isis-module-security.
> The implementation will probably also have to reach into Wicket internals in
> order to obtain details of currently logged on users (assuming that
> information is available).
> If we do rely on Wicket, then there's a question about clustering.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
