At our company network, the roles in Active Directory(AD) are not appropriately assigned for my application. So I created a simple table in my database mapping all the users in the AD and their roles. There is literally only two columns in this table, user and role.
We’re beginning to design a whole bunch of new services to create (WCF, ADO.NET Data Services, possibly in the cloud at some point) and one question that pops up is what authentication and authorization scheme to use – there are quite a few!
I’m building a new ASP.NET MVC application (in C#) and one of the requirements is to create a new database of members. For this, we’d need roles to manage the different types of members and profiles to manage the additional metadata attached to each member. So far so good, just use the standard MembershipProvider, RoleProvider and ProfileProvider provided as part of the .NET Framework.
Is it generally a really bad idea to not use the built-in asp.net membership provider?
In my ASP.NET applications I have following settings in DefaultMembershipProvider and SqlMembershipProvider in web.config:
Evaluting the method signature, it is required to know old password while changing it.
Can I have different login URL for different ASP .NET MVC3 areas?
I am trying to get the Membership Provider to work.
In a website, I need to integrate membership and authentication. So I want to use the functionality of ASP.NET Membership, but I have other custom stuff, that a “user” has to do.
How can I use Membership.GeneratePassword to return a password that ONLY contains alpha or numeric characters? The default method will only guarantee a minimum and not a maximum number of non alphanumeric passwords.