What's the status of the Membership Provider. The documentation refers to a script (tables.sql) to create the needed tables but it or the folder it should be in doesn't exist.
It's this ready to be tested and if so, what tables are needed?
3.50 Beta and ASP.NET Providers
Here is sql script, which creates required tables
Code: Select all
DROP TABLE USERTOROLE;
DROP TABLE SESSIONS;
DROP TABLE MEMBERSHIP;
DROP TABLE ROLES;
DROP TABLE PROFILES;
DROP TABLE ASPNET_USERS;
CREATE TABLE SESSIONS (
SESSIONID VARCHAR(80) NOT NULL,
APPLICATIONNAME VARCHAR(255) NOT NULL,
CREATED DATETIME NOT NULL,
EXPIRES DATETIME NOT NULL,
LOCKDATE DATETIME NOT NULL,
LOCKID DECIMAL NOT NULL,
TIMEOUT DECIMAL NOT NULL,
LOCKED TINYINT NOT NULL,
SESSIONITEMS LONGTEXT,
FLAGS DECIMAL NOT NULL,
constraint SESSIONS_SESSIONID_PK primary key (SESSIONID)
);
CREATE TABLE ASPNET_USERS (
USERID VARCHAR(40) NOT NULL,
APPLICATIONNAME VARCHAR(255) NOT NULL,
USERNAME VARCHAR(245),
LASTACTIVITYDATE DATETIME,
IsAnonymous TINYINT,
constraint ASPNET_USERS_USERID_PK primary key (USERID),
constraint ASPNET_USERS_USERNAME_PK unique (USERNAME, APPLICATIONNAME)
);
CREATE TABLE MEMBERSHIP (
USERID VARCHAR(40) NOT NULL,
PASSWORD VARCHAR(255),
EMAIL VARCHAR(255),
PASSWORDQUESTION VARCHAR(255),
PASSWORDANSWER VARCHAR(255),
COMMENTS VARCHAR(255),
ISAPPROVED TINYINT,
ISLOCKEDOUT TINYINT,
CREATIONDATE DATETIME,
LASTLOGINDATE DATETIME,
LASTPASSWORDCHANGEDDATE DATETIME,
LASTLOCKOUTDATE DATETIME,
FailedPasswordAttemptCount INT,
FailedPasswordAttemptStart DATETIME,
FailedPasswordAnswerCount INT,
FailedPasswordAnswerStart DATETIME,
constraint MEMBERSHIP_USERID_PK primary key (USERID),
constraint MEMBERSHIP_USERID_REF FOREIGN KEY (USERID) REFERENCES ASPNET_USERS (USERID)
);
CREATE TABLE ROLES (
APPLICATIONNAME VARCHAR(255) NOT NULL,
ROLEID VARCHAR(40) NOT NULL,
ROLENAME VARCHAR(245) NOT NULL,
constraint ROLES_ROLEID_PK primary key (ROLEID),
constraint ROLES_ROLENAME_KEY UNIQUE (ROLENAME, APPLICATIONNAME)
);
CREATE TABLE USERTOROLE (
USERID VARCHAR(40) NOT NULL,
ROLEID VARCHAR(40) NOT NULL,
CONSTRAINT USERTOROLE_USERID_REF FOREIGN KEY (USERID) REFERENCES ASPNET_USERS (USERID),
CONSTRAINT USERTOROLE_ROLEID_REF FOREIGN KEY (ROLEID) REFERENCES ROLES (ROLEID),
CONSTRAINT USERIDROLEID_KEY UNIQUE (USERID, ROLEID)
);
CREATE TABLE PROFILES (
USERID VARCHAR(40),
PropertyNames LONGBLOB NOT NULL,
PropertyValuesString LONGBLOB NOT NULL,
PropertyValuesBinary LONGBLOB NULL,
LastUpdatedDate DATETIME NOT NULL,
CONSTRAINT PROFILES_USERID_REF FOREIGN KEY (USERID) REFERENCES ASPNET_USERS (USERID),
CONSTRAINT PROFILES_USERID_KEY UNIQUE (USERID)
);
Thanks for the script. I created the tables but still get a few errors. The first one is from the following attribute:
"passwordFormat="Hashed"
The second is an exception error when using the ASP.NET Configuration tools. When saving a new user, I get the exception error.
I can track these down but don't have access to the source code for the provider.
Is this anyone testing it? Is it working for you?
"passwordFormat="Hashed"
The second is an exception error when using the ASP.NET Configuration tools. When saving a new user, I get the exception error.
I can track these down but don't have access to the source code for the provider.
Is this anyone testing it? Is it working for you?
Providers?
Is it possible to to modify the Profile, Membership, Role Providers to work with my existing database structure?
Thanks.
Thanks.
Membership provider can work only in passwordFormat="Clear" mode now (do not specify passwordFormat parameter in configuration file now). We will fix this in the future.
We reproduced the error when saving new user with ASP.NET Configuration tools. If you received this error then you have entered invalid password for user (it is too short or does not have enough non-alphanumeric symbols). We will fix this in the next MySQLDirect .NET build
We reproduced the error when saving new user with ASP.NET Configuration tools. If you received this error then you have entered invalid password for user (it is too short or does not have enough non-alphanumeric symbols). We will fix this in the next MySQLDirect .NET build
-
- Posts: 4
- Joined: Tue 25 Apr 2006 06:37