User authentication and authorization in Active Directory or database?
We're in the process of rebuilding one of our web services in .Net/MsSQL (from PHP/MySQL). In the redesign discussions the topic of how to handle authentication and authorization has come up several times. In the legacy system there were users, companies, and roles all stored in DB tables. One of the proposals for the new system is to use Active Directory to manage the authentication and authorization and to only have a stub presence in the DB.

Has anyone gone through this migration? Can you point out some of the pros and cons for going to AD from a DB?
User authentication and authorization in Active Directory or database?
===

We're in the process of rebuilding one of our web services in .Net/MsSQL (from PHP/MySQL). In the redesign discussions the topic of how to handle authentication and authorization has come up several times. In the legacy system there were users, companies, and roles all stored in DB tables. One of the proposals for the new system is to use Active Directory to manage the authentication and authorization and to only have a stub presence in the DB.

Has anyone gone through this migration? Can you point out some of the pros and cons for going to AD from a DB?