Check out: DotNetNuke.Entities.Users.UserController.ValidateUser

Just an FYI - what you are planning represents an exploitable security vulnerability in your module:
1. Plain text username, password and verification code
2. username, password, verification code in url parameters
3. exposure of the validation process through a url.

Given that the goal of the verification process is to validate the email address (and thereby the "validity" that the member is a real person with an actual email address) you may consider an alternative.

Personally I think the current portalid-userid verificaiton code represents an "Spoof-able" vulnerability.

Ideally generating something random like a GUID that has a short expiry and then connecting the email to the code would prevent sending plain text information over the wire and limit the lifecycle of the verification process.

Just my 2 cents - not that you asked ;) it's just that I'm in the middle of writing a number of custom reg/login/password recovery modules right now to reduce/remove vulnerabilities.

---

Steven Webster
Manager, Community Platform
F5 Networks, DevCentral

I think the email sent it editable using the languages editor (resource files). You could also write your own verification email and send it from your module.

---

Steven Webster
Manager, Community Platform
F5 Networks, DevCentral