Link to home
Start Free TrialLog in
Avatar of zachvaldez
zachvaldezFlag for United States of America

asked on

user aurhentication and web security

I'm a newbie as far user web authentication and web/internet security areas but my question could either easy or difficult.
So here is it..
I'm developing a registration formthat I'm planning to put on the web . My question is..
How would I be sure that who is login to the site is the right person who claim he is. What authentication structure need to place. In short,for example, if you are login in to your bank under the name 'John Doe',how does the bank know you are John Doe for sure and the name you claim you are.What methods are use to achieve this.
Avatar of disrupt
disrupt
Flag of United States of America image

Take a look at this to get started you can edit your web.config like so:

http://msdn.microsoft.com/en-us/library/xdt4thhy.aspx

This sort of authentication is called forms authentication.

you can get whoever is logged in by:

Page.User.Identity.Name


Avatar of zachvaldez

ASKER

Is forms authentication the best way to go . What are pros and cons?
Why would I take this route? What other alternatives there are for web security and authentication ?
Take a loom at this article

http://msdn.microsoft.com/en-us/library/aa291347(v=vs.71).aspx

Gives you pros and cons of each
Can you provide more info on forms authentication because that may be the only applicable
authentication available?
ASKER CERTIFIED SOLUTION
Avatar of disrupt
disrupt
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I started reading on link I Google but it is ASP.net2.0 and I'm using 4.0 framework
A lot of reading yet to do and lots of assumptions and possibilities to cover..question is..
If someone got my '-password and id,can that be used to login from another Pc? Since the cookies are not in that PC, I assume,he can't get In
You might want to re-phrase your question.
Leaving Biometrics aside, web app does not recognize John Doe, it can recognize only the credentials entered by the user i.e. username and password.

If somebody get's your usename+password, web authentication will allow to login.

FormsAuthentication hasn't changed between 2.0 / 4.0 and neither Asp.NET Membership/Roles Providers. So the older tutorials still stand valid.

Several banks have added an additional layer of security to login e.g.
1:  Secret Question - which you need to answer after you enter username/password
2:  If the website detects you are trying to logging in using different computer, they send you passcode to email or phone on their file. You need to verify this before it allows you to enter the website.
3: Number Matrix: Bank provides you with a card with 4x4 matrix of numbers. When you enter valid username/password, the system shows you e.g. 4x4 matrix with few empty boxes. You are supposed to fill in the boxes using you the card you got.

Hope this helps.
The secret question or Identity image that is displayed to confirm identity,it stored in the database or client cookies?


 
Database
Is that code for secret question in the login page? How about when the user login from a different computer and an email is generated and send to reenter log in details,pw and email address some kind to prove identity
-->Is that code for secret question in the login page?
I would do it in a separate page because say user is trying to login from a login box in master page. But again it depends on your overall design and logic.

-->How about when the user login from a different computer and an email is generated and send to reenter log in details,pw and email address some kind to prove identity

I don't think if it is a good idea to ask user to enter the username+password again.
Whatever you do, make sure you make it clear to user why they are required this second layer of security.