You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am building an application using the Microservices pattern. My application has been broken down into different services including Chat Service to allow users to talk to each other, an authentication service for user and session management, etc. My authentication service has been built on top of Supabase with NestJS while my chat service has been built on top of RocketChat. Once users have been logged in to my application and assigned a session via the authentication service, I want them to be able to use the same session and profile information to be able to chat with each other in-app. Rocket chat however seems to have its own auth set up for user and session identification so users have to somehow reauthenticate with Rocket chat even after authenticating with my application so that they can send peer-to-peer messages to each other. Of course, asking the users to authenticate again once they're already logged in so that they can be able to send texts to each other is not a good user experience. How then can I be able to go round this problem and somehow ensure Rocket chat uses the same user and session details from my authentication service to identify and make user sessions so that they don't have to re-authenticate once they want to start chatting?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am building an application using the Microservices pattern. My application has been broken down into different services including Chat Service to allow users to talk to each other, an authentication service for user and session management, etc. My authentication service has been built on top of Supabase with NestJS while my chat service has been built on top of RocketChat. Once users have been logged in to my application and assigned a session via the authentication service, I want them to be able to use the same session and profile information to be able to chat with each other in-app. Rocket chat however seems to have its own auth set up for user and session identification so users have to somehow reauthenticate with Rocket chat even after authenticating with my application so that they can send peer-to-peer messages to each other. Of course, asking the users to authenticate again once they're already logged in so that they can be able to send texts to each other is not a good user experience. How then can I be able to go round this problem and somehow ensure Rocket chat uses the same user and session details from my authentication service to identify and make user sessions so that they don't have to re-authenticate once they want to start chatting?
Beta Was this translation helpful? Give feedback.
All reactions