You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Dragut Razvan (JIRA)" <ji...@apache.org> on 2009/02/13 15:15:59 UTC

[jira] Updated: (JSEC-59) JSecurity user access to active sessions

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

Dragut Razvan updated JSEC-59:
------------------------------

    Summary: JSecurity user access to active sessions  (was: JSecurity user Access to active sessions)

> JSecurity user access to active sessions
> ----------------------------------------
>
>                 Key: JSEC-59
>                 URL: https://issues.apache.org/jira/browse/JSEC-59
>             Project: JSecurity
>          Issue Type: New Feature
>          Components: Session Management
>            Reporter: Dragut Razvan
>            Priority: Minor
>
> Hi hi,
> As discussed in this thread : http://n2.nabble.com/Subject-Session-relationship-td2303079.html, this feature request refers to accessing the active sessions in JSecurity.
> It would be useful at times to have access to the active sessions and implicitly to subject creation. One of the scenarios that will benefit from this, is to implement features like 'kick' (logout some random users by a super admin). However, currently there is a workaround to implement this using permissions ( see Les' response in thread mentioned above ).
> This feature requires some debate, voting , usage scenarios with weaks/strongs/why/when along with implementation/approach ideas, because it seems it might have performance implications if JSecurity users will be able to iterate in a standard way through potential thousands of sessions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.