KC Wong
Guest
|
Posted:
Wed Nov 24, 2004 9:38 am Post subject:
Can I use profiles other than UserObject for login? |
|
|
Hi all,
I'm new to CS and have problem trying to determine the best way to do
profiling/registration/authentication in the following scenario:
I have a scenario where there are 3 different user types, namely
Business, Non-Businesss and Members.
When registering with the site, users must choose a registration type
and the corresponding user registration screen will pop up (remember
there are 3 different registration screens for the 3 user types,
containing different fields).
Now I'm thinking to create 3 different profile definitions for each of
the user type, meaning each registration will be submitted and updated
to the respective profile according to the registration type. Is this
viable? Or should I just use the UserObject profile and keep
everything in there, and differentiate the user type by a User Type
custom field in UserObject?
Reason for doing this is if I only use UserObject, I would have many
unused fields for every record row (depending on the user type).
Next question then, would be what happens when a user tries to login.
If I use 3 profile definitions to keep profiles of the 3 user types,
it means when attempting to login, i'll have to look into 3
tables/profile definitions to authenticate the user. Is this workable,
or I MUST stick to using only the UserObject profile for login?
Any feedback would be greatly appreciated!
Cheers
KC |
|
David Messner [MSFT]
Guest
|
Posted:
Thu Dec 30, 2004 4:51 am Post subject:
RE: Can I use profiles other than UserObject for login? |
|
|
I think you will find it simpler to use a single profile definition and
just overload it with all properties used for each user type and just allow
them to be null if they are not applicable to the current user type.
In fact the default user profile definition has a UserType property for
similar purpose (registered/anonymous).
-djm
--
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2004 Microsoft Corporation. All rights
reserved.
--------------------
From: kc4775@yahoo.com (KC Wong)
Newsgroups: microsoft.public.commerceserver.general
Subject: Can I use profiles other than UserObject for login?
Date: 23 Nov 2004 19:38:09 -0800
Organization: http://groups.google.com
Lines: 31
Message-ID: <65b4114c.0411231938.406f9cc4@posting.google.com>
NNTP-Posting-Host: 219.93.8.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1101267490 20695 127.0.0.1 (24 Nov 2004
03:38:10 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Wed, 24 Nov 2004 03:38:10 +0000 (UTC)
Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!tornado.fastwebnet.it!tiscali!new
sfeed1.ip.tiscali.net!news.glorb.com!postnews.google.com!not-for-mail
Xref: cpmsftngxa10.phx.gbl microsoft.public.commerceserver.general:15151
X-Tomcat-NG: microsoft.public.commerceserver.general
Hi all,
I'm new to CS and have problem trying to determine the best way to do
profiling/registration/authentication in the following scenario:
I have a scenario where there are 3 different user types, namely
Business, Non-Businesss and Members.
When registering with the site, users must choose a registration type
and the corresponding user registration screen will pop up (remember
there are 3 different registration screens for the 3 user types,
containing different fields).
Now I'm thinking to create 3 different profile definitions for each of
the user type, meaning each registration will be submitted and updated
to the respective profile according to the registration type. Is this
viable? Or should I just use the UserObject profile and keep
everything in there, and differentiate the user type by a User Type
custom field in UserObject?
Reason for doing this is if I only use UserObject, I would have many
unused fields for every record row (depending on the user type).
Next question then, would be what happens when a user tries to login.
If I use 3 profile definitions to keep profiles of the 3 user types,
it means when attempting to login, i'll have to look into 3
tables/profile definitions to authenticate the user. Is this workable,
or I MUST stick to using only the UserObject profile for login?
Any feedback would be greatly appreciated!
Cheers
KC |
|