shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "hujie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SHIRO-627) something wrong with shiro-spring-boot-web-starter,it did not auto register securityManager???
Date Mon, 26 Jun 2017 14:14:01 GMT

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

hujie commented on SHIRO-627:
-----------------------------

I found code from shiro-spring-boot-web-starter:
@Bean
    @ConditionalOnMissingBean
    @Override
    protected Authorizer authorizer() {
        return super.authorizer();
    }
and I tried to debug there,but breakpointer not  triggered,maybe because of “@ConditionalOnMissingBean”。
but boot telled me :org.apache.shiro.spring.web.config.AbstractShiroWebFilterConfiguration
required a bean named 'authorizer' that could not be found. 

> something wrong with shiro-spring-boot-web-starter,it did not auto register securityManager???
> ----------------------------------------------------------------------------------------------
>
>                 Key: SHIRO-627
>                 URL: https://issues.apache.org/jira/browse/SHIRO-627
>             Project: Shiro
>          Issue Type: Question
>          Components: Sample Apps
>    Affects Versions: 1.4.0
>         Environment: windows 7 64bit
> jdk 1.8
>            Reporter: hujie
>              Labels: starter
>             Fix For: 1.4.0
>
>
> {code}
> 2017-06-26 19:59:22.126  INFO 6576 --- [           main] c.p.s.Jsr303HibernateValidateApplication
: Starting Jsr303HibernateValidateApplication on hujie-PC with PID 6576 (D:\jee-git-repo\study\JSR303-Hibernate-Validate\target\classes
started by hujie in D:\jee-git-repo\study\JSR303-Hibernate-Validate)
> 2017-06-26 19:59:22.150  INFO 6576 --- [           main] c.p.s.Jsr303HibernateValidateApplication
: No active profile set, falling back to default profiles: default
> 2017-06-26 19:59:22.232  INFO 6576 --- [           main] ationConfigEmbeddedWebApplicationContext
: Refreshing org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@539d019:
startup date [Mon Jun 26 19:59:22 CST 2017]; root of context hierarchy
> 2017-06-26 19:59:23.586  INFO 6576 --- [           main] trationDelegate$BeanPostProcessorChecker
: Bean 'org.apache.shiro.spring.boot.autoconfigure.ShiroBeanAutoConfiguration' of type [class
org.apache.shiro.spring.boot.autoconfigure.ShiroBeanAutoConfiguration$$EnhancerBySpringCGLIB$$51c46c26]
is not eligible for getting processed by all BeanPostProcessors (for example: not eligible
for auto-proxying)
> 2017-06-26 19:59:23.624  INFO 6576 --- [           main] trationDelegate$BeanPostProcessorChecker
: Bean 'eventBus' of type [class org.apache.shiro.event.support.DefaultEventBus] is not eligible
for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
> 2017-06-26 19:59:23.730  INFO 6576 --- [           main] trationDelegate$BeanPostProcessorChecker
: Bean 'org.apache.shiro.spring.config.web.autoconfigure.ShiroWebAutoConfiguration' of type
[class org.apache.shiro.spring.config.web.autoconfigure.ShiroWebAutoConfiguration$$EnhancerBySpringCGLIB$$7660cc90]
is not eligible for getting processed by all BeanPostProcessors (for example: not eligible
for auto-proxying)
> 2017-06-26 19:59:23.772  INFO 6576 --- [           main] trationDelegate$BeanPostProcessorChecker
: Bean 'localRealm' of type [class cn.points.study.shiro.realms.LocalRealm$$EnhancerBySpringCGLIB$$b0c600bf]
is not eligible for getting processed by all BeanPostProcessors (for example: not eligible
for auto-proxying)
> 2017-06-26 19:59:24.032  INFO 6576 --- [           main] trationDelegate$BeanPostProcessorChecker
: Bean 'sessionStorageEvaluator' of type [class org.apache.shiro.web.mgt.DefaultWebSessionStorageEvaluator]
is not eligible for getting processed by all BeanPostProcessors (for example: not eligible
for auto-proxying)
> 2017-06-26 19:59:24.034  INFO 6576 --- [           main] trationDelegate$BeanPostProcessorChecker
: Bean 'subjectDAO' of type [class org.apache.shiro.mgt.DefaultSubjectDAO] is not eligible
for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
> 2017-06-26 19:59:24.038  INFO 6576 --- [           main] trationDelegate$BeanPostProcessorChecker
: Bean 'subjectFactory' of type [class org.apache.shiro.web.mgt.DefaultWebSubjectFactory]
is not eligible for getting processed by all BeanPostProcessors (for example: not eligible
for auto-proxying)
> 2017-06-26 19:59:24.044  INFO 6576 --- [           main] trationDelegate$BeanPostProcessorChecker
: Bean 'rememberMeCookieTemplate' of type [class org.apache.shiro.web.servlet.SimpleCookie]
is not eligible for getting processed by all BeanPostProcessors (for example: not eligible
for auto-proxying)
> 2017-06-26 19:59:24.049  INFO 6576 --- [           main] trationDelegate$BeanPostProcessorChecker
: Bean 'rememberMeManager' of type [class org.apache.shiro.web.mgt.CookieRememberMeManager]
is not eligible for getting processed by all BeanPostProcessors (for example: not eligible
for auto-proxying)
> 2017-06-26 19:59:24.055  INFO 6576 --- [           main] trationDelegate$BeanPostProcessorChecker
: Bean 'authenticationStrategy' of type [class org.apache.shiro.authc.pam.AtLeastOneSuccessfulStrategy]
is not eligible for getting processed by all BeanPostProcessors (for example: not eligible
for auto-proxying)
> 2017-06-26 19:59:24.060  INFO 6576 --- [           main] trationDelegate$BeanPostProcessorChecker
: Bean 'authenticator' of type [class org.apache.shiro.authc.pam.ModularRealmAuthenticator]
is not eligible for getting processed by all BeanPostProcessors (for example: not eligible
for auto-proxying)
> 2017-06-26 19:59:24.062  WARN 6576 --- [           main] ationConfigEmbeddedWebApplicationContext
: Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException:
Error creating bean with name 'org.apache.shiro.spring.config.web.autoconfigure.ShiroWebFilterConfiguration':
Unsatisfied dependency expressed through field 'securityManager'; nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'securityManager' defined in class path resource [org/apache/shiro/spring/config/web/autoconfigure/ShiroWebAutoConfiguration.class]:
Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException:
Failed to instantiate [org.apache.shiro.mgt.SessionsSecurityManager]: Factory method 'securityManager'
threw exception; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException:
No bean named 'authorizer' is defined
> 2017-06-26 19:59:24.143 ERROR 6576 --- [           main] o.s.b.d.LoggingFailureAnalysisReporter
  : 
> ***************************
> APPLICATION FAILED TO START
> ***************************
> Description:
> Field securityManager in org.apache.shiro.spring.web.config.AbstractShiroWebFilterConfiguration
required a bean named 'authorizer' that could not be found.
> {code}
> ********************************************************************************8
> {code}
> my boot properties :
> shiro.enabled=true
> shiro.web.enabled=true
> shiro.annotations.enabled=false
> shiro.loginUrl=/login.html
> shiro.successUrl=/
> shiro.unauthorizedUrl=/unauthorizedUrl.html
> shiro.userNativeSessionManager=true
> {code}
> I read code of shiro-spring-boot-web-starter,and shiro-spring-boot-starter,and i register
one bean ,type of realm.
> {color:red}but I debug found there is not have securityManager???{color}
> why shiro samples did not register securityManager bean,but it can runing,
> sorry about my english.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message