HOME COMMUNITY BLOG
Skip to end of metadata
Go to start of metadata

This article describes mapping from AspNetMembership tables to OrigamUser table.

OrigamUser ColumnDataTypeAllow NullsAspNetMembership ColumnNote
refBusinessPartnerIduniqueidentifierno Value has to be looked for in Origam BusinessPartner table. It should be searched by UserName.
Passwordnvarchar(100)yes

aspnet_Membership.Password

aspnet_Membership.Salt

Values from Password and Salt column need to be combined into one string with | as separation character: password|salt.

RecordCreatedByuniqueidentifieryes  
RecordUpdatedByuniqueidentifieryes  
Iduniqueidentifierno Primary key.
RecordCreateddatetimeyesaspnet_Membership.CreateDate 
RecordUpdateddatetimeyes  
IsLockedOutbitnoaspnet_Membership.IsLockedOut 
LastLoginDatedatetimeyesaspnet_Membership.LastLoginDate 
LastLockoutDatedatetimeyesaspnet_Membership.LastLockoutDate 
FailedPasswordAttemptCountintnoaspnet_Membership.FailedPasswordAttemptCount 
FailedPasswordAttemptWindowStartdatetimeyesaspnet_Membership.FailedPasswordAttemptWindowStart 
UserNamenvarchar(255)yesaspnet_Users.UserName 
EmailConfirmedbitnoaspnet_Membership.IsApproved 

 

The following sql script could be used to migrate users from aspnet membership database to ORIGAM user database. The script expects to be run connected to your ORIGAM data database and AspNetMembership database to be named as 'aspnetdb'. There could be a problems with different collations of the two databases. In the following example script it's solved by added COLLATE expressions. However if the collation of your databases (ORIGAM data and AspNetMembership) are the same, then all the COLLATE expressions should be ommitted.

Sql Script for migration of users