asp.net mvc - Am I wrong in wanting to roll my own Authenticate / Authorize system given the following requirements? -


In my pet project, I have to have a user system with the following requirement:

  • I want to use DI (through use) to give the necessary dependencies in my user model
  • It should be easy to plug in
  • Without a lot of trouble, it is important to be tested.
  • Anonymous users must support a lot like SO
  • I want certification and authorization
  • It needs to be protected

I know that I'm putting some techniques before some activities here , But as it is a pet project and I want to learn some new things that I think it is appropriate to include them as requirements.

Halfway in my own rolling, I realized that I might have to face some syndrome.
I really do not like how the unnecessary complex current user framework in asp.net, it's actually mostly just about all the more complicated stuff about security which is now giving me some doubt what to go to it And will be able to roll your own? If not, how would you go about completing all the above requirements with the existing opener-based framework?

I like what you want to do, your own custom Roll a Net Subscription Provider.

This will allow you to use the built-in ASP.NET authentication / authorization attribute s giving full control over the implementation within your provider ( Which will allow you to code it to meet the requirements described above).

Directly from MSDN ...


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

php - Multiple Select with Explode: only returns the word "Array" -

php - jQuery AJAX Post not working -