The password gets encrypted in the application code, before it is sent to the DB.  So you would have to catch it there if you wanted it before it is encrypted.

If you are going to be storing it in two different places and want to be more secure, then you should switch to using hashed passwords instead of encrypted ones.

If you don't really care about the security too much, then you could also switch to storing them in clear text.  Then you would have a clear text version in your DB table.

 

---

Well this is the code that looks like creates a new user when the register button is clicked:

Dim userCreateStatus As UserCreateStatus = userCreateStatus.AddUser

'if a user is found with that username, error.
'this prevents you from adding a username
'with the same name as a superuser.
If Not objUserInfo Is Nothing Then
'username already exists in DB so show user an error
UI.Skins.Skin.AddModuleMessage(Me, String.Format(DotNetNuke.Services.Localization.Localization.GetString("RegistrationFailure", Me.LocalResourceFile), userControl.UserName), UI.Skins.Controls.ModuleMessage.ModuleMessageType.YellowWarning)
Exit Sub
End If

Dim AffiliateId As Integer = Null.NullInteger
If Not Request.Cookies("AffiliateId") Is Nothing Then
AffiliateId = Integer.Parse(Request.Cookies("AffiliateId").Value)
End If

Dim objNewUser As New UserInfo
objNewUser.PortalID = PortalId
objNewUser.Profile.FirstName = userControl.FirstName
objNewUser.Profile.LastName = userControl.LastName
objNewUser.Profile.Unit = addressUser.Unit
objNewUser.Profile.Street = addressUser.Street
objNewUser.Profile.City = addressUser.City
objNewUser.Profile.Region = addressUser.Region
objNewUser.Profile.PostalCode = addressUser.Postal
objNewUser.Profile.Country = addressUser.Country
objNewUser.Profile.Telephone = addressUser.Telephone
objNewUser.Email = userControl.Email
objNewUser.Username = userControl.UserName
objNewUser.Membership.Password = userControl.Password
objNewUser.Membership.Approved = Convert.ToBoolean(IIf(PortalSettings.UserRegistration <> PortalRegistrationType.PublicRegistration, False, True))
objNewUser.AffiliateID = AffiliateId
objNewUser.Profile.Cell = addressUser.Cell
objNewUser.Profile.Fax = addressUser.Fax
objNewUser.Profile.IM = userControl.IM
objNewUser.Profile.Website = userControl.Website
objNewUser.Profile.PreferredLocale = cboLocale.SelectedItem.Value
objNewUser.Profile.TimeZone = Convert.ToInt32(cboTimeZone.SelectedItem.Value)

userCreateStatus = UserController.CreateUser(objNewUser)


So the question is, can this work by passing some of these varable sto another stored procedure? And if so, how does all this work? What exactly does the statement "userCreateStatus = UserController.CreateUser(objNewUser)" do? And would something like this work:

' Create Email Account
Dim emailCreateStatus As EmailCreateStatus = emailCreateStatus.AddEmail
Dim objNewEmail As New EmailInfo

objNewEmail.Username = userControl.UserName
objNewEmail.Membership.Password = userControl.Password

emailCreateStatus = UserController.CreateUser_Email(objNewEmail)