Ratchet VS php-jwt

1) Do we must need to use some 3rd Party APIs or Libraries like Ratchet, PHP-Push-WebSocket or PHP WebSocket to enable PHP to communicate over WebSocket protocol?

I am using http://socketo.me/ to create the socket server.

Sockets: https://github.com/reactphp/socket WebSocket: https://github.com/ratchetphp/Ratchet

Have you considered using web sockets? Check out Ratchet PHP http://socketo.me/. Once the client and server make a connection your server can send notifications to the client while that connection is open.

How should I implement these functions? I am successful with using this documentation to implement basic websocket functions. However, I am still unable to subscribe to a channel/topic. The code is long so I put a github question here. Hope that you can help me with this.

You can do native websockets with PHP, but it's not straightforward with Laravel. Laravel Echo helps handle the client-side of websockets, but you need to manage the server side on your own.

Nice work. I have something similar I built on Ratchet, I looked at Socket.io in the early days but shelved plans to run a Node backend. Your front end looks a lot more appealing than mine does. ;)

However, the websockets server is based on a php package http://socketo.me/ , and sometimes that mini-app goes down without warning, leaving the chat to fallback to an old-school chat-archive. Even monitoring and being certain that the chat websocket server is -up- isn't obvious.

Hello, I have just start to learn web socket in php but I have one issue I would use a secure web socket for https pages but one their website: https://socketo.me They use a class, MyChat but vscode doesn’t find it. Does anybody know ? Thanks

Which implementation would you like? * http://socketo.me/ * https://amphp.org/websocket-client/ * https://www.swoole.co.uk/docs/modules/swoole-websocket-server

So basically if the login is successfull I have to create a JWT token (with something like this library) with the userID inside and send it via `setcookie()` for web or in a JSON response to the API client and consider it the long lived refresh token.

This depends on the library you end up downloading for the platform of your choosing. Some of the parts I explained above will be handled by the library for example in my case I decoded signedTransactionInfo using firebase/php-jwt. This has the added benefit of always checking the validity of the signature which was omitted in the manual method.

https://github.com/firebase/php-jwt i use this one, its really good

> Why all the hate for JWTs?

> Just pick a crypto scheme and the JWT is just an encoding that makes it easier to use.

That's not what JWT is, but I can understand why someone would be misled into believing that.

JWT isn't just an encoding format, it also includes a crypto algorithm negotiation protocol that lets the attacker choose the algorithm. Even if you strictly allow-list which algorithm you want to support, you can accidentally bypass this control in many libraries if you suppor the `kid` (key ID) header. [1]

It also allows attackers to completely strip the security. [2] [3]

Put shortly, JWT is a gun aimed directly at your foot. That's why there's so much hate for JWTs.

[1] https://github.com/firebase/php-jwt/issues/351

[2] https://paragonie.com/blog/2017/03/jwt-json-web-tokens-is-ba...

[3] https://www.howmanydayssinceajwtalgnonevuln.com/