shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Erickson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SHIRO-297) Setting sessionMode to native kills any SessionManager already configured
Date Tue, 17 May 2011 01:18:47 GMT

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

Jason Erickson updated SHIRO-297:
---------------------------------

    Description: 
I just got done working through an issue trying to get single sign-on working with EhCacheManager,
following some examples I found on the mailing list (except I was using Spring configuration).
 It wasn't working for me at first with this: 

{code:xml}
<bean id="securityManager" 
  class="org.apache.shiro.web.mgt.DefaultWebSecurityManager"> 
     <property name="realm" ref="factorlabRealm" /> 
     <property name="subjectFactory" ref="factorlabSubjectFactory" /> 
     <property name="cacheManager" ref="ssoCacheManager" /> 
     <property name="sessionManager" ref="sessionManager" /> 
     <property name="sessionMode" value="native" /> 
</bean> 
{code}

 
After lots of debugging, I got it to work with this: 
 
 
<bean id="securityManager" 
  class="org.apache.shiro.web.mgt.DefaultWebSecurityManager"> 
    <property name="sessionMode" value="native" /> 
    <property name="realm" ref="factorlabRealm" /> 
    <property name="subjectFactory" ref="factorlabSubjectFactory" /> 
    <property name="cacheManager" ref="ssoCacheManager" /> 
    <property name="sessionManager" ref="sessionManager" /> 
</bean> 
 
 
The difference is moving the sessionMode to earlier in the property list, because the setter
for sessionMode was replacing my configured 
sessionManager with a new DefaultWebSessionManager.   

This seems pretty fragile.


  was:
I just got done working through an issue trying to get single sign-on working with EhCacheManager,
following some examples I found on the mailing list (except I was using Spring configuration).
 It wasn't working for me at first with this: 


<bean id="securityManager" 
  class="org.apache.shiro.web.mgt.DefaultWebSecurityManager"> 
     <property name="realm" ref="factorlabRealm" /> 
     <property name="subjectFactory" ref="factorlabSubjectFactory" /> 
     <property name="cacheManager" ref="ssoCacheManager" /> 
     <property name="sessionManager" ref="sessionManager" /> 
     <property name="sessionMode" value="native" /> 
</bean> 
 
 
After lots of debugging, I got it to work with this: 
 
 
<bean id="securityManager" 
  class="org.apache.shiro.web.mgt.DefaultWebSecurityManager"> 
    <property name="sessionMode" value="native" /> 
    <property name="realm" ref="factorlabRealm" /> 
    <property name="subjectFactory" ref="factorlabSubjectFactory" /> 
    <property name="cacheManager" ref="ssoCacheManager" /> 
    <property name="sessionManager" ref="sessionManager" /> 
</bean> 
 
 
The difference is moving the sessionMode to earlier in the property list, because the setter
for sessionMode was replacing my configured 
sessionManager with a new DefaultWebSessionManager.   

This seems pretty fragile.



> Setting sessionMode to native kills any SessionManager already configured
> -------------------------------------------------------------------------
>
>                 Key: SHIRO-297
>                 URL: https://issues.apache.org/jira/browse/SHIRO-297
>             Project: Shiro
>          Issue Type: Bug
>    Affects Versions: 1.0.0, 1.1.0
>            Reporter: Jason Erickson
>
> I just got done working through an issue trying to get single sign-on working with EhCacheManager,
following some examples I found on the mailing list (except I was using Spring configuration).
 It wasn't working for me at first with this: 
> {code:xml}
> <bean id="securityManager" 
>   class="org.apache.shiro.web.mgt.DefaultWebSecurityManager"> 
>      <property name="realm" ref="factorlabRealm" /> 
>      <property name="subjectFactory" ref="factorlabSubjectFactory" /> 
>      <property name="cacheManager" ref="ssoCacheManager" /> 
>      <property name="sessionManager" ref="sessionManager" /> 
>      <property name="sessionMode" value="native" /> 
> </bean> 
> {code}
>  
> After lots of debugging, I got it to work with this: 
>  
>  
> <bean id="securityManager" 
>   class="org.apache.shiro.web.mgt.DefaultWebSecurityManager"> 
>     <property name="sessionMode" value="native" /> 
>     <property name="realm" ref="factorlabRealm" /> 
>     <property name="subjectFactory" ref="factorlabSubjectFactory" /> 
>     <property name="cacheManager" ref="ssoCacheManager" /> 
>     <property name="sessionManager" ref="sessionManager" /> 
> </bean> 
>  
>  
> The difference is moving the sessionMode to earlier in the property list, because the
setter for sessionMode was replacing my configured 
> sessionManager with a new DefaultWebSessionManager.   
> This seems pretty fragile.

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

Mime
View raw message