Can anyone tell what is the difference between ASP.NET Website Administration tool's VS Enterprise library 5.0 security application block (in terms of authentication and authorization ?
Thanks
Please don't forget to mark this as "ANSWER." "Sharing is caring..."
FIrst off the Website Admin Tool is nothing but a few pages that use the built-in asp.net methods and functions to create users, roles, assign roles to users, etc. The
Security Application Block essentially provides an engine to authenticate a user against different membership providers.
Remember to mark as answer if this post answered or solved your problem.
Thanks for the reply. My requirement is to create an authentication and authorisation (AA) module which can use both SQL and AD membership. Now my understanding is that security application block allows you to do this via a ui tool. You then have to use
the enterprise library dlls to write the code for the AA (authorize, validate etc). The same can be acheived by using membership providers offered by System.web.security namespace ? So, Is the system.web.security (AA) different from security application block's
AA. Does the security application block use the classes from system.web.security under the hood?
(Note: leaving the caching of AA to a side for a moment provided by enterprise library)
Please don't forget to mark this as "ANSWER." "Sharing is caring..."
Angad Bhat
Member
593 Points
146 Posts
Website Administration tool VS Security Application block 5.0
Feb 22, 2012 02:36 PM|LINK
Can anyone tell what is the difference between ASP.NET Website Administration tool's VS Enterprise library 5.0 security application block (in terms of authentication and authorization ?
Thanks
"Sharing is caring..."
Thank you!
b471code3
Star
13877 Points
2598 Posts
Re: Website Administration tool VS Security Application block 5.0
Feb 22, 2012 07:27 PM|LINK
FIrst off the Website Admin Tool is nothing but a few pages that use the built-in asp.net methods and functions to create users, roles, assign roles to users, etc. The Security Application Block essentially provides an engine to authenticate a user against different membership providers.
Angad Bhat
Member
593 Points
146 Posts
Re: Website Administration tool VS Security Application block 5.0
Feb 23, 2012 08:53 AM|LINK
Hi there,
Thanks for the reply. My requirement is to create an authentication and authorisation (AA) module which can use both SQL and AD membership. Now my understanding is that security application block allows you to do this via a ui tool. You then have to use the enterprise library dlls to write the code for the AA (authorize, validate etc). The same can be acheived by using membership providers offered by System.web.security namespace ? So, Is the system.web.security (AA) different from security application block's AA. Does the security application block use the classes from system.web.security under the hood?
(Note: leaving the caching of AA to a side for a moment provided by enterprise library)
"Sharing is caring..."
Thank you!