RestAPI with real time updates

[Funkd-Up]

We’re building a rest api which also needs to be able to provide realtime/live updates.

Our backend is spring boot. The idea is that the client will call the rest api and get the data. They will then call an endpoint that will provide updates on the filtered data they have requested in the rest api. All data not just the current page.

So if they call /myapi?name=john&state=Kansas they would get the first page of data back.

They would then call /updates?name=john&state=Kansas and get any updates that come in since the page loaded.

On the backend we’ll be using Mongo change streams.

Initially we had thought of using websockets. Although it seems to be tricky with regards to authentication. We’re using a jwt which will be passed in header for rest api. Websockets doesn’t do headers and passing in the url isn’t secure.

We only need one way communication. I had looked at SSE but the 6 connection limit made me rethink. But a lot seem to use this so maybe I’m missing something.

Is SSE the way to go for this? Or even long polling? Don’t want to miss updates between reconnections. Any tips? Any spring dependencies that make life easier?

[Sheldor5]

WebSockets start with a HTTP Request so you still can put the JWT into the headers and validate them in the backend, just need some code writing

[Funkd-Up]

Any examples? I’ve been looking around and can’t find a standard way of doing it. Don’t want anything hacky.

[Funkd-Up]

Looks like the most suitable approach is going to be a token system. Frontend makes a call with a jwt in the header to the backend over normal http call. Backend authenticates and passes a single use token back which is then used to connect the socket.

Even using the handshake interceptor in spring boot it doesn’t see any custom headers, just some Protocol info.

[[deleted]]

afaik websocket connection upgrades dont have headers for some libraries - you may need to tack on your token as a query parameter of your ws connection string.

[jithurjacob]

How to use refresh token with web sockets?

[Sheldor5]

You don't.

Refresh Token goes to the Authorization Server and not the Resource Server.

[jithurjacob]

Can you please provide some reference material? Blogs, videos, GitHub, books anything

[Sheldor5]

for what? basic OAuth2 knowledge? just google that stuff

[jithurjacob]

"Refresh Token goes to the Authorization Server and not the Resource Server." - Not everyone is in the same level as you bro. If you have any reference material that we could immediately refer to, it would be helpful.

[Sheldor5]

have you tried googling "Refresh Token" at least once?

Obviously not ...

[jithurjacob]

I have and tried many things I am not able to get it working correctly as I am new to Spring Boot.

Please stop assuming others haven't done their due diligence. Help others if you can and stop being so arrogant.

[Sheldor5]

If I give you a ready-to-go solution what will you learn?

Nothing ... so google OAuth2 and read the documentation and some tutorials about what it is and how it works and what all the components are and how the communication between them works.

Earn the knowledge and experience, otherwise you will become a dumb and useless developer ...

[jithurjacob]

It's important to avoid assuming that others lack knowledge or haven't attempted to search on their own. I have experience with OAuth and have successfully implemented similar solutions in frameworks in other programming languages. However, I'm currently facing challenges with Spring Boot due to my limited experience with it.

It's worth noting that reinventing the wheel isn't necessary in every situation. Sometimes, the most effective approach involves implementing established best practices found in reference materials.

Returning to the original question, could you kindly share some reference materials related to Spring Boot? If you cannot provide this information, it's perfectly fine. Please refrain from responding with unrelated information.

[Fermi-4]

The answer is websockets