Currently, we're using cookie-signature npm package to sign the session-id. It attaches the actual string with the encrypted string. Hence we're planning to change this approach.
One of the possible solutions is saving actual str along with encrypted str in the session store instead of attaching it within the session-id.
Currently, we're using cookie-signature npm package to sign the session-id. It attaches the actual string with the encrypted string. Hence we're planning to change this approach.
One of the possible solutions is saving actual str along with encrypted str in the session store instead of attaching it within the session-id.