• Share
  • Email
  • Embed
  • Like
  • Private Content
Building A Membership Provider For DotNetNuke 4.X.X
 

Building A Membership Provider For DotNetNuke 4.X.X

on

  • 3,857 views

During this talk Henry will be creating a fully functional Membership Provider for DotNetNuke illustrating the pluggable nature of the Provider Model. The talk will begin with some theory as well as ...

During this talk Henry will be creating a fully functional Membership Provider for DotNetNuke illustrating the pluggable nature of the Provider Model. The talk will begin with some theory as well as solidifying reasons why you should or even need to build a new provider. Henry will create a working sample that authenticates against a totally different data source. Presented by Henry Kenuam of Engage Software.

Statistics

Views

Total Views
3,857
Views on SlideShare
3,842
Embed Views
15

Actions

Likes
0
Downloads
30
Comments
0

1 Embed 15

http://www.slideshare.net 15

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Building A Membership Provider For DotNetNuke 4.X.X Building A Membership Provider For DotNetNuke 4.X.X Presentation Transcript

    • Building a Membership Provider for DNN 4.x.x. presented by Henry Kenuam, Engage Software
    • About Me • Henry Kenuam – CTO at Engage Henry Kenuam: hkenuam@engagesoftware.com Engage Software p:: 314.966.4000 x224 f:: 314.966.2299 www.engagesoftware.com
    • Objective for the next Hour • What is Membership? • Understanding all the Pieces • DNN Authentication features and settings • Walk through the DNN Login process • Create a new Membership Provider (from default). • Modify new provider code to use Web Services for authentication. • Tidbits on DNN Extension (Cambrian)
    • What is Membership? • Membership is one small piece of larger objective • Single Sign-on is about passing credentials for site to site or portal to portal. • Authentication System – Term for encapsulating authentication process
    • Considerations • Why am I replacing the membership (authentication) in the first place? • Who ultimately will manage users? DNN or the remote system? • Can I achieve what I need by adding on to the existing functionality provided or am I replacing the user's data store and the validation process entirely? • Does the other system provide enough functionality to satisfy the abstract Membership Provider that DNN uses? • Can I retrieve a decrypted password from the new data store?
    • Understanding all the Pieces • Default Authentication for DNN is Forms Authentication • Built on the ASP.NET 2.0 Membership • DNN uses a Provider Model to allow new implementation plug-in • Membership Provider, Role Provider and Profile Provider, providers, providers, providers…
    • Enough talk, let’s look at some code…
    • Additional References • http://msdn.microsoft.com • http://www.engagemodules.com • http://www.charlesnurse.com/ • http://odetocode.com/Articles/427.aspx