当您使用REST API和JWT时,如何在春季将stolds websocket会话复制到redis

时间:2017-02-08 03:45:48

标签: spring-boot redis stomp spring-websocket spring-session

我正在构建一个小的websocket项目,并通过JWT令牌机制进行保护,我想在redis中存储websocket会话而不是本地内存。

@Override
protected void configureStompEndpoints(StompEndpointRegistry registry) {
    registry
            .addEndpoint("/hello")
            .addInterceptors(new HttpSessionHandshakeInterceptor() {
                @Override
                public boolean beforeHandshake(ServerHttpRequest request, ServerHttpResponse response,
                        WebSocketHandler wsHandler, Map<String, Object> attributes) throws Exception {
                    if (request instanceof ServletServerHttpRequest) {
                        ServletServerHttpRequest servletRequest = (ServletServerHttpRequest) request;
                        HttpSession session = servletRequest.getServletRequest().getSession();
                        attributes.put("sessionId", session.getId());
                    }
                    return true;
                }
            })
            .withSockJS()
            .setSessionCookieNeeded(true);
}

我的redis配置中的@EnableRedisHttpSession和上面的源代码安全地将http会话存储在redis中,但即使我刷新了我的redis数据库,我仍然可以向我连接的客户端发送和接收我的消息。

我的猜测是HttpSession与WebSocket会话不同。我应该如何聪明地&#34;如果您使用基于令牌的身份验证,请求spring以redis存储和维护与websocket相关的会话?

更新1

StompHeaderAccessor accessor =
                    MessageHeaderAccessor.getAccessor(message, StompHeaderAccessor.class);

            List<String> tokenList = accessor.getNativeHeader("username");
            accessor.removeHeader("username");

            String username = null;
            if (tokenList != null && tokenList.size() > 0) {
                username = tokenList.get(0);
            }

            AuthenticationToken authToken = new AuthenticationToken(username);
            SecurityContextHolder.getContext().setAuthentication(authToken);

            switch(accessor.getCommand()) {
                case CONNECT:
                    Principal auth = username == null ? null : authToken;
                    accessor.setUser(auth);

                    return MessageBuilder.createMessage(message.getPayload(), accessor.getMessageHeaders());
                case CONNECTED:
                    System.out.println("Stomp connected");
                    break;
                case DISCONNECT:
                    System.out.println("Stomp disconnected");
                    break;
                case SEND:
                    break;
                default:
                    break;
            }
            return message;

更新2

我认为STSP上的Websocket依赖于SimpSessionId而不是握手拦截器中创建的HttpSession。

StompHeaderAccessor [headers={simpMessageType=MESSAGE, stompCommand=SEND, nativeHeaders={username=[*******], destination=[/app/feed], content-length=[81]}, simpSessionAttributes={SPRING.SESSION.ID=187912de-a875-45ef-995a-7723fd8715c8}, simpHeartbeat=[J@6e9173e4, simpUser=***.AuthenticationToken@1767840c: Principal: *******; Credentials: [PROTECTED]; Authenticated: true; Details: null; Not granted any authorities, simpSessionId=d686qam8, simpDestination=/app/feed}]

更新3

SimpUserRegistry说这是&#34;当前连接用户的注册表。&#34;这可能是答案吗?

更新4

我正在使用RabbitMQ。这是否意味着我在做什么是完全没用的?

0 个答案:

没有答案