As a followup on this issues, I would also like to find out if there is a way for us to set our oen rule for generation of the verification number that is being sent. Right now it seems to be using PortalID and UserID combination as a default, I may be wrong but thats what it seems to derive its logic from.

I would like to know if we can set our own rule to generate this number so that the verification process in DNN can be made a little more difficult to guess, even though a combinaton of this and the account lock out on x number of fialed login attempts make is sufficiently cumbersome for someone trying to gain access, I guess if there is a need for higher security then one can use the "Private" setting to approve users manually, but it would be nice to know if it was possible to set our own rule to generate the verification code, in case a higher security is needed for a high traffic site where approving users manually may be too resource intensive.

AGM

Thanks Leupold,

I did some digging in the sourcecode and found the verification code in the AspNetMembershipProvider.vb so I guess when the user registers the logic uses the portalID and userID combo and sends that as verification code in the email and then when the user logs in for the first time it does the cross check of these 2 values and as they already exist as ID's they don't need to be stored anywhere. Got it...

Thanks for all your responses

AGM