@fedect1 I wouldn't give out a userId in the REST path because it's the primary identifier for every action within the app. I.e. someone technically versed might misuse that to do operations for that user or retrieve more details. Send the userId at least hidden with the request parameters.
To completely hide that information you would use JSON Web Token that only transfers an encrypted session token that u decode in the backend to verify the user and validity of the session.
@fedect1 I wouldn't give out a userId in the REST path because it's the primary identifier for every action within the app. I.e. someone technically versed might misuse that to do operations for that user or retrieve more details. Send the userId at least hidden with the request parameters.
To completely hide that information you would use JSON Web Token that only transfers an encrypted session token that u decode in the backend to verify the user and validity of the session.
postHandler.js