Re: Manually adding a ASP.Membership account for an install script

On Feb 19, 1:32 pm, "sloan" <sl...@xxxxxxxxx> wrote:
One way to do this is to actually add

System.Web
and all the <membership> xml to a CONSOLE app or Windows Form app.

And then you can code against the membership provider, and get this default
data in.

......

I do this for an application.
The client gives me a list of users, their default password, and a user to
role mapping.
(I give them the list of roles).

I actually wrote a (company owned) text file parser that does the work for
me.

.................

The TSQL stuff.

I got this to work one time, but I was using plain passwords. So maybe
someone else can help with that.

"DotNetNewbie" <snowman908...@xxxxxxxxx> wrote in message

news:48b68d25-2432-427c-99e2-eb8a011a9c72@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hello,

I am having issues with manually creating a membership user using the
stored procedure: aspnet_Membership_CreateUser

I can't seem to be able to insert a 'password salt' value and have it
work when I try and log in.

Here is what I did: After creating a user and being able to
successfully log into my application, I looked in the database for the
Password Salt.

I then used that SAME value along with username in my install.sql
script file (it just preloads the database with data).

My login doesn't work though, what could the problem be?

Basically for this application, we have to have the 'admin' user
account preloaded in the database on fresh installs. So I am trying to
create a data.sql script that will load the database, and I want to
setup the admin user account with username: admin and password: change

And I am using non-clear passwords, so I am confused as to why me
putting the same values as what my database has now in the script
doesn't work (login fails when I setup the database).
.

Relevant Pages

  • Re: Sorting out security
    ... > MS Access security. ... > created a new workgroup, added a password for the Admin role, added ... > remote logins to a secured database. ... The location of the current workgroup file is recorded in the ...
    (microsoft.public.access.security)
  • Re: user level security wizard
    ... the name of the database in this shortcut was not the copy, ... But the error message you got I thought was in reference to the mdw file, ... you said that every mdw file has the admin user and the Users Group ... and the security wizard does this for you. ...
    (microsoft.public.access.security)
  • Sorting out security
    ... MS Access security. ... created a new workgroup, added a password for the Admin role, added groups, ... user IDs and passwords for users and allocated permissions on the ... remote logins to a secured database. ...
    (microsoft.public.access.security)
  • Re: Help - Pathworks & Windows 2000 Advanced Server
    ... Your privilege level on domain TURPINS-WM is ADMIN. ... The partial synchronization replication of the LSA database from the ...
    (comp.os.vms)
  • Re: Problems setting up access security
    ... The Admin user still owns the database object. ... You secured it using the system.mdw, thinking that you were using your secure mdw. ...
    (microsoft.public.access.security)