I would like to use the Role Membership and User Security database as my application database too. That is, just add the tables and relationships required by my application's data access layer to the Membership and Roles Database to save on hosting fees, (I have to pay extra for having two databases instead of one). Of course, the connection string would have to be adjusted, but I don't see a downside considering the application's database is actually an Access database. What can I say, it was a requirement at the time.
Basically, I would like to do the opposite of this: http://forums.asp.net/p/1162485/1925262.aspx#1925262
I am making a simple ASP.NET webpage for my school organization using VS2010. When I choose "New Website," I see that Visual Studio already sets up a database for managing memberships. I also have my own database (MyDatabase) that I need to use for the site, which contains information about the members of the organization (for example, email, phone-number, etc.)
I need to have a way to find out who the current logged-in user is, and allow them to edit ONLY their information (email, phone-number).The way I have considered doing it is:
- Add a field in MyDatabase called "UserName" and use it as a sort-of foreign key from the other database.
- Get the username of the logged-in user
- Use this username for my queries For example:
// (PseudoCode) String loggedInUser = MembersDatbase.GetLoggedInUser(); var MemberInfo = SELECT * FROM MyDatabase.Users WHERE UserName=loggedInUser;
-Then the logged-in user will only have access to their information.
I'm not sure about the code yet, but I could probably figure that part out. I'm more interested in hearing if there is a better way of doing this. I do NOT want to merge the two databases into a single database.
This is a very common error as evidenced but the very large number of problems and suggested solutions on the web. I finally got around it last week but can't remember what was the step that did it. At that time, I was building a web application rather than a web site. Is that the difference? As you can see, it is no longer in the APP_DATA folder and is named membership.mdf rather than aspnetdb.mdf. I ran aspnet_regsql.exe to create it and actually had it working and was updating it successfully. But for other reasons, I had to scrap the application and decided to re-create it from scratch as a web site rather than a web application. I had been using Visual Studio 2008 to build the web application but am now using Visual Web Developer 2008 Express Edition to build the web site. Unfortunately, the Visual Studio application will no longer open so I can't verify that the web application still works. Can anybody help? (Please!!!) BTW, ASPNET and NETWORK SERVICE both have full control over the membership.mdf.
I installed sql server express 2008 R2, no problems.
I created a database and added a table, no problems.
I'm using the entity framework, I created and am using the .edmx file, no problems.
I created a form that reads from and submits to the table, no problems.
I added the membership tables to the database, now I have problems.
I can still read from and update my table fine, so clearly the connection string in my web.config still works. But I can't add a new user or do anything with the website administration tool. It can't find any providers, and under security, it tells me it can't login into the database. When I try to register a new user, I get a failed login error, again for my database user. Yet I can login fine through Server Management Studio with the same credentials.
I was reading through this post here http://www.misfitgeek.com/op-ed/adding-asp-net-membership-to-your-own-database and thought to my self what the common practice is. What do developers using ASP.NET membership and authorization in their applications recommend as a best practice? creating the membership tables in the same database that stores their applications data or configuring a second database to store ONLY the membership information?.
My current setup is a different database for membership information ONLY but am thinking that increases the number of databases i have to maintain. If I have 5 applications using asp.net membership, then that means 5 more asp.net membership databases. So do you normally create the asp.net membership tables in your main database or you configure a separate membership table? what do you recommend.
When a user is registered in an MVC application using the default Register action of the Account controller, where is the user info stored? Can I specify that this user table be stored in the database of the MVC application?
I am reading about writing a custom membership provider. I want to have some linkage between application specific user info ( current orders, items the user has ordered ) and the login database. I want to hook the "register a new user" process so that a new customer is added to the customer master.
thisUser gives me access to all the fields in aspnet_Membership. I want a new field, isSubscribed for each user. I can use an SQL query to fetch the value fine, but I want to know if there is someway to modify the membershipuser object so it retrieves this value as well, so it is accessible from:
Is it possible to use the Membership API with an already exisiting database? I have a database that is built around my own fields for the User and breaks down users into half a dozen different groups that determine their access to different parts of the site and exactly what they can do and see on different pages.
I'm currently working on a membership system for my web application, which is based on forms authentication from the framework.I created some users with the integrated tool, and the login is perfectly working. But now what I want to do is to give administrator the capability to create, modify, delete users.So here is what I've got right now:
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load Dim muc As MembershipUserCollection = Membership.GetAllUsers() ComboBox1.DataSource = muc [code]....
The problem is that the record doesn't seem to be updated in the database.I made the multiple calls to Membership.UpdateUser after reading this blog entry, but it didn't change anything.A strange thing I noticed while debugging, is that when I enter the Button1_Click method, Membership.GetUser(userName) returns me values from my precedent attempt !
ASPNETDB Problem - Unable to connect to SQL Server database
now, after some real soul searching, i managed to get it working, however i want to do the following:
I have a table in a database I created called "Students". Now, I have a studentId and a password in that table. What I want to do is allow users to login using their accounts.
However, I am having real trouble doing this. I want to create a custom membership provider, etc.
I have been crawling through the net looking for ways to do it but some of the sites I visited had too much complicated code.
I am facing a very unique situation and need help. My problem is as follows:1. I have a basic ASP.NET website (3.5 is it helps on IIS 7) where I have implemented Membership for Authentication.2. The site caters to multiple companies (Say Company A, Company B etc.).3. For each company I need to have different database (SQL 2008). This is mandatory as i can use multiple Application in there.Now as far as the flow is concern its pretty simple:1. The user comes to this site with a QueryString like cid=123 (in actual there is a HttpModule for this, cid=123 is just for this forum purpose).2. The site using the cid=123 gets to know this user is for Company A (i have a WCF service for this, how it works is not a problem.), along with that I also get the connectionstring for the database this user should use.3. For Business implementation i have handled this nicely in my DAL Layer.4. The problem comes with Membership.5. In Membership I have writtent a custom provider, that assigns the connection on teh fly.6. But this happens only once for the application. i.e. the connectio string gets cached at application level.7. The connection string does not change untill I reset my IISwhere i can have a single WebSite, catering to different companies, using seperated databases and using Membership for Authorization.
public class CustomMembershipProvider : SqlMembershipProvider { public override void Initialize(string name, System.Collections.Specialized.NameValueCollection config)
I want to add custom columns to some tables created by ASP.NET. For example; I need to add two fields such as FirstName and LastName to the aspnet_Membership table.
I can add this directly by editing the table but;
Is this the right thing to do (I mean; extending the table directly) OR should I create a separate table and hold the extra user data, there?How can I see these custom database fields as properties in code completion? example: membershipuser.FirstName;
I am attempting to add a database to the AppData folder. It seems to only want to use SQL Express, which I have read is not a good idea for a live website for the purposes of memberships. How do I change the default Express to SQL2008.
I've just finished my database design and now i'm going to start implementing it in SQL Server 2008. Since i'm creating an ASP.NET Web Application i would like to use Membership Provider to manage user access to the application. In other projects (more simpler) i used Membership but always with its default parameters.
In this recent application i need to use custom user data for it to work properly.
So, what i would like to know is, how can i use my 'Users' table in my DB with .NET Membership Provider?
I am new to using the membership provider. I have been working in a small shop that has very focused programming and we are starting to venture out as our needs have grown. My question is the following:
Once I have created the asp schema and I set up users. How do I perform database access using those user accounts? I know how to perform access using a database account (schema), but do not understand how to use a user that only exists in a user table to access data tables.
Do I use an anonymous account and control access on the front end?
I'm trying to plan a series of websites that all share many of the resources such as css/jscript/images/content etc. For this reason I wanted to run all of the websites under the same application and IIS profile, but depending on the URL being used change the masterpage and theme/skin.
The ASP.NET membership database seems as if it was designed with this goal in mind because it allows you to setup multiple applications, however I believe the purpose for which this was built was to allow applications to be run under virtual directories/fodlers, not on seperate urls.
this might seem REALLY simple but i'm not a genius...anyway, i know i saw this somewhere: here's what i want to do: link the web.config file to my membership database...which i am going to put on a separate server on the network.
I am in the initial stage of implementing a new webstie, which will use only twitter and facebook to login and use. So my approach is not use any Default memberhip database, just simple store the user data in my created "membership" database. I will set cookies and use sessions to restrict and grant access to various parts of the sites. So for example, the user creates an account and I set a cookie allowing him or her to traverse the site. And on each page request from the client browser check to see if my website cookie is there in the browser and if it has expired or not.