Alternative to Ip address of client

Question

1.00/5 (1 vote)

See more:

i have an existing web service in which i used username , password and Ip address of user for authenticating user identity,now i am moving my web services to cloud and the ip address of client will changing according to load is there any alternating for ip address for authenticating user?

Posted 11-Dec-14 5:51am

Member 10506003

Add a Solution

Comments

Kornfeld Eliyahu Peter 11-Dec-14 12:22pm

Why username and password not satisfy you?

Member 10506003 15-Dec-14 6:21am

Actually we are providing services to clients and client have many users so for tracking all the users we match the ip address of the client to ensure client's user is validate or not.If we only use username name and password then it not ensure the client's user is validate because all have same username and password also we have to track by which client the request is coming or and user belong to which client.

Kornfeld Eliyahu Peter 15-Dec-14 6:27am

Your real problem is the 'same username and password' part...

ZurdoDev 11-Dec-14 12:41pm

I agree. Why care about anything more than just username and password?

Member 10506003 15-Dec-14 6:21am

Actually we are providing services to clients and client have many users so for tracking all the users we match the ip address of the client to ensure client's user is validate or not.If we only use username name and password then it not ensure the client's user is validate because all have same username and password also we have to track by which client the request is coming or and user belong to which client.

ZurdoDev 15-Dec-14 7:30am

You may already know this but all clients from one office will likely have the same IP address.

Sergey Alexandrovich Kryukov 11-Dec-14 18:40pm

Don't use IP. This is not fair. And is the abuse. Use only username and password. If you want to add more security, establish the system using also the client-side certificate...
—SA

Member 10506003 15-Dec-14 6:24am

Actually we are providing services to clients and client have many users so for tracking all the users we match the ip address of the client to ensure client's user is validate or not.If we only use username name and password then it not ensure the client's user is validate because all have same username and password also we have to track by which client the request is coming or and user belong to which client.After using client side certificate it didn't full fill my requirement.Anything By which we can track client's user identity.
Thanks for reply

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2014-12-15T05:27:00

Member 10506003 wrote:

Actually we are providing services to clients and client have many users so for tracking all the users we match the ip address of the client to ensure client's user is validate or not. If we only use username name and password then it not ensure the client's user is validate because all have same username and password also we have to track by which client the request is coming or and user belong to which client. After using client side certificate it didn't full fill my requirement. Anything By which we can track client's user identity.

Sorry, such considerations look ridiculous. Why? When you create a new user profile and a new person gives you the user name matching one of existing names, you show "user name already exist" message and deny account creation. This is how it's done everywhere.

Tracking the user by IP is counter-productive, because 1) the same user often changes IP (especially these days when people become more and more mobile), 2) most users use dynamic IP addresses, so the same user can have different IP address at different time at the same location; so, at different moments of time, the same user uses different IP addresses and different users can have the same IP address.

Besides, your arguments apparently contradict your own observations and your formulation of the problem. It looks like you fully realize what's going on and only are reluctant to accept it.

—SA