Question: Once a user successfully authenticates against a web application, they are typically provided with an authentication token (i.e. a session ID). Anyone holding that ID
Once a user successfully authenticates against a web application, they are typically provided with an authentication token (i.e. a session ID). Anyone holding that ID can impersonate the authenticated user. What steps should an application author take to protect that ID as it is stored in either the client or server or as it is transmitted between them?
Step by Step Solution
There are 3 Steps involved in it
Get step-by-step solutions from verified subject matter experts
