Root routing for token authentication

Question

0.00/5 (No votes)

See more:

Hello Friends,

I am beginner into MVC 4.0 and wanted to authenticate a user while accessing my web application on http. I am having an object with key values(username, permissions, token,secure key). I want to pass these information in top parent route so it can be accessable to every http post/get request to authenticate every request. But not using COOKIES.

Thank you !

Chandrakant

Posted 19-Mar-13 0:37am

Chandrakant Kumawat

Add a Solution

1 solution

Add a Solution

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)

**Zoltán Zörgő** · Answer 1 · 2013-03-19T02:24:00

You should follow the asp.net built-in authentication concepts. This does not mean, that you can use only the built-in membership and role providers. As I see you will have to build your own custom providers at least that for membership.
Here are the general concepts of it: http://msdn.microsoft.com/en-us/library/f1kyba5e(v=vs.100).aspx[^]
And here are two samples you could start from: Custom Membership Providers[^], Custom MembershipProvider and RoleProvider Implementations that use Web Services[^]
And of course, you can set up asp.net authentication to be cookie-less (independent of the provider itself), see: http://msdn.microsoft.com/en-us/library/aa479314.aspx[^]