Comments by sohst - CodeProject

sohst 24-Apr-12 3:56am View

Hi Philippe, we assume that a 'new' company (i.e. a new customer of the web service) will be created at once with its first 'employee' (or 'delegate'), to whom the system necessarily assigns the role as administrator, because he is the first one having the faculties to create new users and manage all kind of data. Of course, he can delegate these faculties by creating another administrative user. Any delegate can belong only to one company.

Basically, Mark already indicated the way how to manage the logon process (see his comment). Actually, what is called 'users' in the common logon database, will then contain the registered companies as the real customers, and the new table could be named 'delegates' or 'employees', pointing to their referring customer-users. Is it this what you suggested?

sohst 23-Apr-12 16:39pm View

Gotcha. I'll continue following your third proposal, i.e. modifying the stored proc in the ASP.NET authentication database. That seems to me quite straight forward and at least for me the easiest way, too. Thanks again, Mark.

sohst 23-Apr-12 15:55pm View

Thanks for your comment, Mark. - OK, if in the first step a qualified user (say, a representative of a company) registers his company, these data will be stored in some database table that can be referred to by himself and the other employees to register as "real" users. That means, the built-in authentication logic of APS.NET would be used only for the employees. But how do I extend the common login procedure to store the reference of an employee to his company in his user credentials?

Comments by sohst (Top 3 by date)