How to close Websocket connections on failed authentication?












0















I'm setting up my spring boot application. The problem I have with my app is that WebSocket connections are still open after failed spring security authentication.
I didn't authenticate the user before this in order to test the application in non-standard situations.



My configuration requires "USER" role for CONNECT command.



@Override
protected void configureInbound(MessageSecurityMetadataSourceRegistry messages) {
messages
.nullDestMatcher().hasRole("USER")
.simpDestMatchers("/app/info").hasRole("USER")
.simpSubscribeDestMatchers("/user/queue/info").hasRole("USER")
.anyMessage().denyAll();
}


I expected the closed connection on server side, but received the following message on client side:



"<<< ERROR
content-length:0
message:Failed to send message to ExecutorSubscribableChannel[clientInboundChannel]; nested exception is org.springframework.security.access.AccessDeniedExceptionc Access is denied
content-length:0



... and connection is still active.



To confirm the connection is active, I used @EventListener:



@EventListener
public void onDisconnectEvent(SessionDisconnectEvent event) {
// print debug message
}


...and closed the connection manually on client side. I was able to see the closed connection stack trace again:



// print debug message



+



org.springframework.messaging.MessageDeliveryException: Failed to send message to ExecutorSubscribableChannel[clientInboundChannel]; nested exception is org.springframework.security.access.AccessDeniedException: Access is denied
at ...



I think this is a problem and I don’t want my app to maintain connections with hundreds of non authenticated sockets.










share|improve this question



























    0















    I'm setting up my spring boot application. The problem I have with my app is that WebSocket connections are still open after failed spring security authentication.
    I didn't authenticate the user before this in order to test the application in non-standard situations.



    My configuration requires "USER" role for CONNECT command.



    @Override
    protected void configureInbound(MessageSecurityMetadataSourceRegistry messages) {
    messages
    .nullDestMatcher().hasRole("USER")
    .simpDestMatchers("/app/info").hasRole("USER")
    .simpSubscribeDestMatchers("/user/queue/info").hasRole("USER")
    .anyMessage().denyAll();
    }


    I expected the closed connection on server side, but received the following message on client side:



    "<<< ERROR
    content-length:0
    message:Failed to send message to ExecutorSubscribableChannel[clientInboundChannel]; nested exception is org.springframework.security.access.AccessDeniedExceptionc Access is denied
    content-length:0



    ... and connection is still active.



    To confirm the connection is active, I used @EventListener:



    @EventListener
    public void onDisconnectEvent(SessionDisconnectEvent event) {
    // print debug message
    }


    ...and closed the connection manually on client side. I was able to see the closed connection stack trace again:



    // print debug message



    +



    org.springframework.messaging.MessageDeliveryException: Failed to send message to ExecutorSubscribableChannel[clientInboundChannel]; nested exception is org.springframework.security.access.AccessDeniedException: Access is denied
    at ...



    I think this is a problem and I don’t want my app to maintain connections with hundreds of non authenticated sockets.










    share|improve this question

























      0












      0








      0








      I'm setting up my spring boot application. The problem I have with my app is that WebSocket connections are still open after failed spring security authentication.
      I didn't authenticate the user before this in order to test the application in non-standard situations.



      My configuration requires "USER" role for CONNECT command.



      @Override
      protected void configureInbound(MessageSecurityMetadataSourceRegistry messages) {
      messages
      .nullDestMatcher().hasRole("USER")
      .simpDestMatchers("/app/info").hasRole("USER")
      .simpSubscribeDestMatchers("/user/queue/info").hasRole("USER")
      .anyMessage().denyAll();
      }


      I expected the closed connection on server side, but received the following message on client side:



      "<<< ERROR
      content-length:0
      message:Failed to send message to ExecutorSubscribableChannel[clientInboundChannel]; nested exception is org.springframework.security.access.AccessDeniedExceptionc Access is denied
      content-length:0



      ... and connection is still active.



      To confirm the connection is active, I used @EventListener:



      @EventListener
      public void onDisconnectEvent(SessionDisconnectEvent event) {
      // print debug message
      }


      ...and closed the connection manually on client side. I was able to see the closed connection stack trace again:



      // print debug message



      +



      org.springframework.messaging.MessageDeliveryException: Failed to send message to ExecutorSubscribableChannel[clientInboundChannel]; nested exception is org.springframework.security.access.AccessDeniedException: Access is denied
      at ...



      I think this is a problem and I don’t want my app to maintain connections with hundreds of non authenticated sockets.










      share|improve this question














      I'm setting up my spring boot application. The problem I have with my app is that WebSocket connections are still open after failed spring security authentication.
      I didn't authenticate the user before this in order to test the application in non-standard situations.



      My configuration requires "USER" role for CONNECT command.



      @Override
      protected void configureInbound(MessageSecurityMetadataSourceRegistry messages) {
      messages
      .nullDestMatcher().hasRole("USER")
      .simpDestMatchers("/app/info").hasRole("USER")
      .simpSubscribeDestMatchers("/user/queue/info").hasRole("USER")
      .anyMessage().denyAll();
      }


      I expected the closed connection on server side, but received the following message on client side:



      "<<< ERROR
      content-length:0
      message:Failed to send message to ExecutorSubscribableChannel[clientInboundChannel]; nested exception is org.springframework.security.access.AccessDeniedExceptionc Access is denied
      content-length:0



      ... and connection is still active.



      To confirm the connection is active, I used @EventListener:



      @EventListener
      public void onDisconnectEvent(SessionDisconnectEvent event) {
      // print debug message
      }


      ...and closed the connection manually on client side. I was able to see the closed connection stack trace again:



      // print debug message



      +



      org.springframework.messaging.MessageDeliveryException: Failed to send message to ExecutorSubscribableChannel[clientInboundChannel]; nested exception is org.springframework.security.access.AccessDeniedException: Access is denied
      at ...



      I think this is a problem and I don’t want my app to maintain connections with hundreds of non authenticated sockets.







      spring-security spring-websocket stomp






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 2 at 18:47









      Lucas MabreyLucas Mabrey

      12




      12
























          0






          active

          oldest

          votes












          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54011609%2fhow-to-close-websocket-connections-on-failed-authentication%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54011609%2fhow-to-close-websocket-connections-on-failed-authentication%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          MongoDB - Not Authorized To Execute Command

          How to fix TextFormField cause rebuild widget in Flutter

          in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith