How to use one session token to reference properties stored in a server side cache

Question

0.00/5 (No votes)

See more:

how to use one session token to reference properties stored in a server side cache?.
for ASP.Net Web application.

This is for to prevent URL manipulation(manipulation of parameters exchanged between client and server such as user credentials and permissions),

I'm new to this section please help me in this.

What I have tried:

already AES algorithm encryption is happening
ex-

Response.Redirect("Orderpage.aspx?rno=" + objsecurity.Encrypt(trans_no));

Posted 24-Oct-18 1:04am

Virendra S from Bangalore, Karnataka

Add a Solution

Comments

F-ES Sitecore 24-Oct-18 8:18am

If you are saving things in the Session to stop url tampering you might as well just hold your trans_no in the Session and only do a redirect to Orderpage.aspx. It looks like your actual solution is to implement authentication of some sort to control who can see what.

Richard Deeming 25-Oct-18 13:54pm

There is absolutely no way that credentials and permissions should ever be passed in the URL!

The credentials should only be passed once, when the user logs in, using a POST request to an HTTPS endpoint. The server should validate the credentials, and issue an encrypted cookie which can be used to authenticate the user and determine their permissions entirely on the server.

ASP.NET Identity[^] will already do all of this for you.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)