Привет, у меня проблема с обновляющим токеном в OAuth2.oauth2 token store clash (JPA vs inMemory)
Чтобы получить свежую фишку, я использую следующий запрос: {{хост}}/OAuth/маркер grant_type = refresh_token & refresh_token = [refresh_token_obtained_from_authorization]
Ответ, который я получил это:
{
"error": "server_error",
"error_description": "UserDetailsService is required."
}
в журналах можно увидеть:
2016-10-24 23:01:41.166 DEBUG 48384 --- [nio-8080-exec-7] o.s.orm.jpa.JpaTransactionManager : Creating new transaction with name [org.springframework.security.oauth2.provider.token.DefaultTokenServices.refreshAccessToken]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; '',+org.springframework.security.oauth2.common.exceptions.InvalidTokenException,+org.springframework.security.oauth2.common.exceptions.InvalidGrantException
2016-10-24 23:01:41.166 DEBUG 48384 --- [nio-8080-exec-7] o.s.orm.jpa.JpaTransactionManager : Opened new EntityManager [[email protected]] for JPA transaction
2016-10-24 23:01:41.166 DEBUG 48384 --- [nio-8080-exec-7] o.h.e.t.internal.TransactionImpl : begin
2016-10-24 23:01:41.166 DEBUG 48384 --- [nio-8080-exec-7] o.s.orm.jpa.JpaTransactionManager : Exposing JPA transaction as JDBC transaction [org.springframewo[email protected]5ad1aa88]
2016-10-24 23:01:41.167 DEBUG 48384 --- [nio-8080-exec-7] o.s.s.authentication.ProviderManager : Authentication attempt using org.springframework.security.web.authentication.preauth.PreAuthenticatedAuthenticationProvider
2016-10-24 23:01:41.167 DEBUG 48384 --- [nio-8080-exec-7] p.PreAuthenticatedAuthenticationProvider : PreAuthenticated authentication request: org.springframework.security[email protected]7a6d6be4: Principal: org.springframew[email protected]95dbc1ee: Principal: [email protected]: Username: forkflit; Password: [PROTECTED]; Enabled: true; AccountNonExpired: true; credentialsNonExpired: true; AccountNonLocked: true; Granted Authorities: FORK_FLIT; Credentials: [PROTECTED]; Authenticated: true; Details: {grant_type=password, scope=trust, username=forkflit}; Granted Authorities: FORK_FLIT; Credentials: [PROTECTED]; Authenticated: true; Details: null; Granted Authorities: FORK_FLIT
2016-10-24 23:01:41.167 DEBUG 48384 --- [nio-8080-exec-7] o.s.orm.jpa.JpaTransactionManager : Initiating transaction rollback
2016-10-24 23:01:41.167 DEBUG 48384 --- [nio-8080-exec-7] o.s.orm.jpa.JpaTransactionManager : Rolling back JPA transaction on EntityManager [[email protected]]
2016-10-24 23:01:41.167 DEBUG 48384 --- [nio-8080-exec-7] o.h.e.t.internal.TransactionImpl : rolling back
2016-10-24 23:01:41.167 DEBUG 48384 --- [nio-8080-exec-7] o.s.orm.jpa.JpaTransactionManager : Closing JPA EntityManager [[email protected]] after transaction
2016-10-24 23:01:41.167 DEBUG 48384 --- [nio-8080-exec-7] o.s.orm.jpa.EntityManagerFactoryUtils : Closing JPA EntityManager
2016-10-24 23:01:41.167 DEBUG 48384 --- [nio-8080-exec-7] .m.m.a.ExceptionHandlerExceptionResolver : Resolving exception from handler [public org.springframework.http.ResponseEntity<org.springframework.security.oauth2.common.OAuth2AccessToken> org.springframework.security.oauth2.provider.endpoint.TokenEndpoint.postAccessToken(java.security.Principal,java.util.Map<java.lang.String, java.lang.String>) throws org.springframework.web.HttpRequestMethodNotSupportedException]: java.lang.IllegalStateException: UserDetailsService is required.
2016-10-24 23:01:41.167 DEBUG 48384 --- [nio-8080-exec-7] .m.m.a.ExceptionHandlerExceptionResolver : Invoking @ExceptionHandler method: public org.springframework.http.ResponseEntity<org.springframework.security.oauth2.common.exceptions.OAuth2Exception> org.springframework.security.oauth2.provider.endpoint.TokenEndpoint.handleException(java.lang.Exception) throws java.lang.Exception
2016-10-24 23:01:41.167 INFO 48384 --- [nio-8080-exec-7] o.s.s.o.provider.endpoint.TokenEndpoint : Handling error: IllegalStateException, UserDetailsService is required.
Когда я пытаюсь поставить токен обновления внутри тела: {"refresh_token":"[refresh_token]"}
в ответ я получил:
{
"error": "server_error",
"error_description": null
}
и в журнале:
2016-10-24 23:05:19.449 DEBUG 48384 --- [nio-8080-exec-8] o.s.orm.jpa.JpaTransactionManager : Creating new transaction with name [org.springframework.security.oauth2.provider.token.DefaultTokenServices.refreshAccessToken]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; '',+org.springframework.security.oauth2.common.exceptions.InvalidTokenException,+org.springframework.security.oauth2.common.exceptions.InvalidGrantException
2016-10-24 23:05:19.449 DEBUG 48384 --- [nio-8080-exec-8] o.s.orm.jpa.JpaTransactionManager : Opened new EntityManager [[email protected]] for JPA transaction
2016-10-24 23:05:19.449 DEBUG 48384 --- [nio-8080-exec-8] o.h.e.t.internal.TransactionImpl : begin
2016-10-24 23:05:19.449 DEBUG 48384 --- [nio-8080-exec-8] o.s.orm.jpa.JpaTransactionManager : Exposing JPA transaction as JDBC transaction [org.springframewo[email protected]36a9af25]
2016-10-24 23:05:19.449 DEBUG 48384 --- [nio-8080-exec-8] o.s.orm.jpa.JpaTransactionManager : Initiating transaction rollback
2016-10-24 23:05:19.449 DEBUG 48384 --- [nio-8080-exec-8] o.s.orm.jpa.JpaTransactionManager : Rolling back JPA transaction on EntityManager [[email protected]]
2016-10-24 23:05:19.449 DEBUG 48384 --- [nio-8080-exec-8] o.h.e.t.internal.TransactionImpl : rolling back
2016-10-24 23:05:19.450 DEBUG 48384 --- [nio-8080-exec-8] o.s.orm.jpa.JpaTransactionManager : Closing JPA EntityManager [[email protected]] after transaction
2016-10-24 23:05:19.450 DEBUG 48384 --- [nio-8080-exec-8] o.s.orm.jpa.EntityManagerFactoryUtils : Closing JPA EntityManager
2016-10-24 23:05:19.450 DEBUG 48384 --- [nio-8080-exec-8] .m.m.a.ExceptionHandlerExceptionResolver : Resolving exception from handler [public org.springframework.http.ResponseEntity<org.springframework.security.oauth2.common.OAuth2AccessToken> org.springframework.security.oauth2.provider.endpoint.TokenEndpoint.postAccessToken(java.security.Principal,java.util.Map<java.lang.String, java.lang.String>) throws org.springframework.web.HttpRequestMethodNotSupportedException]: java.lang.NullPointerException
2016-10-24 23:05:19.450 DEBUG 48384 --- [nio-8080-exec-8] .m.m.a.ExceptionHandlerExceptionResolver : Invoking @ExceptionHandler method: public org.springframework.http.ResponseEntity<org.springframework.security.oauth2.common.exceptions.OAuth2Exception> org.springframework.security.oauth2.provider.endpoint.TokenEndpoint.handleException(java.lang.Exception) throws java.lang.Exception
2016-10-24 23:05:19.450 INFO 48384 --- [nio-8080-exec-8] o.s.s.o.provider.endpoint.TokenEndpoint : Handling error: NullPointerException, null
Интересная вещь, что весна делает что-то с JPA, в то время как в моей конфигурации я использую inMemory()
... Что Spring хочет от БД?
Это мой класс конфигурации:
@Configuration
@EnableAuthorizationServer
@EnableResourceServer
@EnableGlobalMethodSecurity(prePostEnabled = true)
public class OAuth2Configuration extends AuthorizationServerConfigurerAdapter {
private UsersService service = new UsersService();
@Autowired
AuthenticationManagerBuilder authenticationManager;
@Override
public void configure(AuthorizationServerEndpointsConfigurer endpoints) {
endpoints.authenticationManager(new AuthenticationManager() {
@Override
public Authentication authenticate(Authentication authentication) throws AuthenticationException {
logger.info("Authentication!");
return authenticationManager.getOrBuild().authenticate(authentication);
}
});
}
@Override
public void configure(ClientDetailsServiceConfigurer clients) throws Exception {
clients.inMemory().withClient("myApp")
.authorizedGrantTypes("password", "refresh_token")
.scopes("write", "read", "trust")
.secret("123456").accessTokenValiditySeconds(200);
}
@Bean
public UserDetailsService userDetailsService() {
return (username) -> {
return service.getByName(username).map(account -> new User(account.getUsername(), account.getPassword(), account.getAuthorities())).orElseThrow(
() -> new RuntimeException("User not found")
);
};
}
}
В журналах я вижу, что Bean создан:
2016-10-24 22:53:49.648 DEBUG 48384 --- [ main] o.s.b.f.s.DefaultListableBeanFactory : Creating shared instance of singleton bean 'userDetailsService'
2016-10-24 22:53:49.648 DEBUG 48384 --- [ main] o.s.b.f.s.DefaultListableBeanFactory : Creating instance of bean 'userDetailsService'
2016-10-24 22:53:49.648 DEBUG 48384 --- [ main] o.s.b.f.s.DefaultListableBeanFactory : Returning cached instance of singleton bean 'org.springframework.transaction.config.internalTransactionAdvisor'
2016-10-24 22:53:49.648 DEBUG 48384 --- [ main] o.s.b.f.s.DefaultListableBeanFactory : Returning cached instance of singleton bean 'OAuth2Configuration'
2016-10-24 22:53:49.653 DEBUG 48384 --- [ main] o.s.b.f.s.DefaultListableBeanFactory : Eagerly caching bean 'userDetailsService' to allow for resolving potential circular references
2016-10-24 22:53:49.654 DEBUG 48384 --- [ main] o.s.b.f.s.DefaultListableBeanFactory : Returning cached instance of singleton bean 'org.springframework.transaction.config.internalTransactionAdvisor'
2016-10-24 22:53:49.654 DEBUG 48384 --- [ main] o.s.b.f.s.DefaultListableBeanFactory : Returning cached instance of singleton bean 'org.springframework.transaction.config.internalTransactionAdvisor'
2016-10-24 22:53:49.655 DEBUG 48384 --- [ main] o.s.b.f.s.DefaultListableBeanFactory : Finished creating instance of bean 'userDetailsService'
У меня нет одной вещи ... Если бы у меня не было UserDetailsService, я не смог бы получить access_token с использованием учетных данных пользователя, а также с помощью refresh_token (с использованием учетных данных работает правильно) –
Тогда это не должно быть из-за отсутствия UserDetailsService, просто отсутствует конфигурация, на стороне сервера не используется HTTP-метод, который запрашивает ваш клиент? – wonhee