Hello Everybody,
In my project I have to use a custom db structure, so I can not use a SQLMembershipProvider. Due to that I have to implement my own provider - unfortunately it is quite a workload. Therefore I have a question - why would you do it? Why not simply omit the whole asp membership, and write your own login/authentication? Is that some kind of security threat? Is asp login component+membership somewhat seafer then just two textboxes (normal + password) that call some function in my business logic layer (naybe the login component makes some kind of encryption or something)? Because if not, I would not even bother trying to implement the MembershipProvider - aspecially that I would have to make some walkarounds and patches in order to make it work (I have looked at it).
Thanks in advance for any replies,
Jozef A. Habdank
...
Go to the complete details ...