Page 2 of 2 FirstFirst 12
Results 11 to 12 of 12

Thread: error: No OAuth 2 security context has been established

  1. #11

    Default

    What I wanted to say in previous post, is that even if your application has properly defined filter, it may still now work. If you have SimpleMappingExceptionResolver configured (without any mappedHandlers and mappedHandlerClasses),
    then it will not rethrow AccessTokenRequiredException
    then filter will not catch this exception and retrieve access token.

  2. #12
    Join Date
    Jun 2005
    Posts
    4,230

    Default

    Correct. If Spring Security cannot catch its own AuthenticationException and AccessDeniedException a lot of features don't work as expected. It's a common mistake in general with Spring Security and not really an OAuth specific concern, I think.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •