In short, I cannot intercept the action associated with a user verification in our custom Membership Provider.

==================================================

We have upgraded to DNN 6.2x from DNN 5.x. We have a custom membership provider because we have another database and we intercept properties to update/insert our other database with values.

This is how our registration process has worked:

1) A person registers a new user and is sent a verification email. (We populate our seperate CRM database at the same time with the user info.)

2) The person uses the link in the email to return to our web site and must enter a password and logs in. At that point we use a overridden version of the UserLogin function in the Membership Provider. We inerrogate the Membership.Approved value of a UserInfo object, and if it is false we assume that the user is not verified and we insert more values into our CRM database.


I know that we have a complicated process, but that is the way it is.

3) At this point an individual in our company reviews the website users and further, manually will set more permissions on the website for the user.

================

Now that we are implementing DNN 6.2.x, there is a new verification model. The user is sent a link. The user then copies the link into a URL, hits return, and magically the user is verified by DNN, and the user did not have to even log in.


Now, in our UserLogin in our membership provider, the user is always approved when we check the Membership.Approved value, and actually that seems like the wrong place to check that.

Where then is the best place to intercept that "Verification" step so that we can update our CRM database?

Thanks