If some specificity helps, here is what I ultimately want to make happen:
- One of our insurance company's existing policy holders wants to registers on our site.
- He goes to the registration page and enters values for the standard DNN registration fields (User Name, First Name, Last Name, etc), along with our site's custom required fields: Client Number, Ssn, Policy Number, DOB, etc.
- When the form is filled out, he clicks the "Register" button.
- The resulting code that executes when "Register" is clicked takes the field values--especially the custom field values--and sends them as parameters to a business layer call that makes sure the policy holder has entered the right information. This validation may be additional business logic processing, web service calls, or database queries to our own tables (in or out of the DNN database), or a combination of all of these.
That's what I want to have happen. I have been able to create a class that inherits from AspNetMembershipProvider, and use it as the membership provider (by changing the "dotnetnuke, members" tag in the DNN web.config). But I don't know if that is the right approach, and I don't know how to create and then access the custom fields I need to include in the registration form.
Any ideas?