shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Les Hazlewood (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (SHIRO-266) Login/Logout: Enable pluggable Subject state binding
Date Sat, 02 Jul 2011 19:54:22 GMT

    [ https://issues.apache.org/jira/browse/SHIRO-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059116#comment-13059116
] 

Les Hazlewood edited comment on SHIRO-266 at 7/2/11 7:53 PM:
-------------------------------------------------------------

Made the following changes today:

- Ensured that direct calls to the HttpServletRequest will honor 'noSessionCreation' filter
settings as well (i.e. httpServletRequest.getSession() or httpServletRequest.getSession(true)).

- Added noSessionCreation checks to WebUtils, but with big warnings (and prefixing with an
underscore) to indicate it is not intended to be used by Shiro end users.

- Changed NoSessionCreationFilter alias in the DefaultFilter enum to be 'noSessionCreation'
instead of 'noSession'.  It is more verbose but more accurate - it doesn't disable all session
usage, just creating them (i.e. another part of the app may create a session that can still
be used).

- Updated the gmaven plugin and actually enabled it for Maven builds (Groovy-based test cases
were not being run from the command line - only in the IDE.  Now they run via command line
builds as expected).

      was (Author: lhazlewood):
    Made the following changes today:

- Ensured that direct calls to the HttpServletRequest will honor 'noSessionCreation' filter
settings as well (i.e. httpServletRequest.getSession() or httpServletRequest.getSession(true)).
- Added noSessionCreation checks to WebUtils, but with big warnings (and prefixing with an
underscore) to indicate it is not intended to be used by Shiro end users.
- Changed NoSessionCreationFilter alias in the DefaultFilter enum to be 'noSessionCreation'
instead of 'noSession'.  It is more verbose but more accurate - it doesn't disable all session
usage, just creating them (i.e. another part of the app may create a session that can still
be used).
- Updated the gmaven plugin and actually enabled it for Maven builds (Groovy-based test cases
were not being run from the command line - only in the IDE.  Now they run via command line
builds as expected).
  
> Login/Logout: Enable pluggable Subject state binding
> ----------------------------------------------------
>
>                 Key: SHIRO-266
>                 URL: https://issues.apache.org/jira/browse/SHIRO-266
>             Project: Shiro
>          Issue Type: Improvement
>          Components: Session Management, Subject
>    Affects Versions: 1.0.0, 1.1.0, 1.1.1
>            Reporter: Les Hazlewood
>            Assignee: Les Hazlewood
>             Fix For: 1.2.0
>
>
> After login, a subject's state (principals, authentication state, etc) are bound to the
Subject's session.  This allows Shiro to reconstruct the Subject instance later on by acquiring
a Session (e.g. by id) and reconstructing the Subject based on the Session's state.
> In stateless environments (e.g. some REST-enabled applications), it is not desirable
to create a session.  There should be a pluggable component that performs state binding and
unbinding for subject login and logout, respectively.  Stateless applications can choose to
configure Shiro with a stateless binder if they don't want sessions to be created.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message