anymessage | AnyMessage lets anybody send and receive messages | SMS library

There are two options:

1) Check the log file from the DSS datadir (for example /PATH-TO-YOUR-DSS-FOLDER/ run/ log)

2) Reach out to the iku admin if you're unable to debug the issue.

They are usually responsive & get things sorted asap!

I was able to enable token based authentication, following the recomendations by Raman on this question. Here's the final code to make it work:

1) First, create a class that represent the JWS auth token:

I suppose you send client requests from different port, that means your client is on different origin, for that you must add some headers on server side. Also on connect websocket sends POST to endpoint, which you must enable. I don't know exactly what endpoints are being sent, check in you console, and then add them to antMatchers

A conversation ID is generated as soon as you install the bot to the Team and you can capture it in OnTurnAsync().

Using App Studio, I got my bot to this part of the install process (after selecting the team and just before selecting the channel to install to):

And I got this in OnTurnAsync:

It also falls through to OnConversationUpdateActivityAsync().

However, it can only converse in the General channel because that's what the conversation ID is tied to upon install. NO activities are fired when installed to a non-General channel within a Team.

Additionally, the activities fired when installed to a Team are only fired once per App Registration App ID, EVER. If you want to test this again, you need an entirely new app registration.

So to answer your question, "yes, if you want the Conversation ID for the General Channel," but "no, if you want the Conversation ID for any other channel".

Sorry to disturb, parameter "connection" in main.js should be http://localhost:8080.

In my opinion: a push messaging pattern (for example using STOMP) is suitable for this scenario, but that ultimately depends on your architectural principles. You could also poll the server for result (using REST API) which has both advantages (shared security architecture) and disadvantages (client code, traffic, and reaction-time overheads).

Answer:

In order to get your code working, I think you need one more method in your SocketConfig.java, which will hook into your OAUTH filter (or whatever method you may have in place).

Important - websocket auth does not reuse existing Spring Security context. That's why you need to implement auth again, for example in the SocketConfig class using the WebSocketMessageBrokerConfigurer's method configureClientInboundChannel.

The following example assumes you have already obtained the OAUTH token previously, and it's only used to reauthenticate the websocket connection. Setting the user reference in StompHeaderAccessor (3rd last line) will enable your code to send a message to the correct user.

It also requires that the OAUTH token is set in the message header, as opposed to the endpoint parameter in your example. I think that may be safer for websocks messaging as the message itself is encrypted on protocol level if you use wss.

The posts you linked works for spring 5 websockets as well and is the simplest solution to extend AbstractSecurityWebSocketMessageBrokerConfigurer

for example:

You have this in your dependencies:

If you use the Akka Kafka consumer, the source emits events indefinitely as far as events are available in the topic. Why do you need to close the producer?

I´ll suggest to call the following to start your source: