how to restrict user when they are not allow to use that aspx page in my application asp.net4.0

Question

3.00/5 (1 vote)

See more:

hi,
how to restrict user when they are not allow to use that aspx page in my application asp.net4.0. there are 4 type users all are having different type of access level, so how to protect from un outherized user.

Posted 24-Jul-12 20:07pm

pradeep040186

Add a Solution

Comments

Sergey Alexandrovich Kryukov 25-Jul-12 2:13am

And what part of this feature would be a problem? What did you try so far?
--SA

2 solutions

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2012-07-24T20:12:00

This is one of the possible solutions:
http://stackoverflow.com/questions/8954728/asp-net-authentication-to-allow-prevent-page-access-and-show-hide-link-at-the-sa[^].

Alternatively, you can redirect the user to a different page (such as "access denied") depending on the user's privileges. Here is how:
http://stackoverflow.com/questions/4834387/how-to-redirect-users-to-an-asp-net-page-when-not-authorized[^].

Perhaps, the most general solution would be generating different page content for different classes of users, which you can always do in your code-behind.

—SA

Prasad_Kulkarni · Answer 2 · 2012-07-24T20:14:00

Solution 2

Introduction to Membership [^] gives you a built-in way to validate and store user credentials, it includes a Role provider which allows you to classify users as you require.

Also Refer:
ASP.NET authentication and authorization[^]
Form authentication and authorization in ASP.NET[^]

Authentication and Authorization in ASP.NET[^]
Authentication and Authorization in ASP.NET[^]
An Overview of Authentication and Authorization Options in ASP.NET[^]

MSDN: Building Secure ASP.NET Applications: Authentication, Authorization, and Secure Communication[^]

More on CodeProject Searqch[^]

Posted 24-Jul-12 20:14pm

Prasad_Kulkarni

Comments

Sergey Alexandrovich Kryukov 25-Jul-12 2:16am

Useful reading, my 5, but the main OP's problem is not the authentication itself but its use.
I suggested some more pin-pointed solutions, please see.
--SA

Prasad_Kulkarni 25-Jul-12 2:28am

Thank you SA!
As per OP's question he require different access levels for his 4 users. So I thought the authorization will help him to move on.

Sergey Alexandrovich Kryukov 25-Jul-12 2:32am

Sure, I already said it's helpful; I just focused on the less obvious and more essential aspect: what to do with the pages to be restricted.
--SA

Prasad_Kulkarni 25-Jul-12 2:37am

No, you said useful reading (but not helpful answer :( ). I also given direction with essential aspect (hmm, but failed with less obvious one).

Sergey Alexandrovich Kryukov 27-Jul-12 17:20pm

OK, OK, I said that. Helpful or not, depends on some other factors, but it's helpful generally. The OP might already know about authentication or not.
--SA