title: In DotNetNuke, what is the difference between a authentication provider and membership provider?
body: <p>I'm working with a product owner who has an existing ASP.NET web application that does some reporting.  For sake of discussion, let's call this "WebApp1."</p>
  
  <p>She has requested that we provide a DotNetNuke portal to provide forum functionality.</p>
  
  <p>As part of the requirements, the main login screen for the DotNetNuke portal should authenticate the user against the user database of "WebApp1."  The existing users table of "WebApp1" has hashed passwords.</p>
  
  <p>As I have been researching these requirements, I have discovered that both MemberShipProvider pattern and AuthenticationProvider seem to address the same requirements.</p>
  
  <p>From a DotNetNuke perspective, what is the difference between these providers?  Which pattern introduces the least complexity?</p>
  
  <p>Please know that my experience with DotNetNuke is limited.</p>
  
  <p>Please know that I'm thankful to the StackOverflow community for your help.</p>