Security :: Hou To Create A Registration Page For Multiple Web Sites
Nov 16, 2010
I created a resiter.aspx page and active.aspx page. a user that register recieve authenticetion email and only after verifying the using a link verification (redirevt to active.aspx page) only then the user authenticated.
This pages are tested and working!
How can I use this page for several solutions? of course I can copy/past this pages. but then I will have to maintain the same code twice....I am looking for the best way to achieve
I want to create a registeration page in asp.net(2.0) without login controls. How it can be done? I have another querry, regarding user details. I want where user information is stored. Can i open that table?
I have created two iis web sites (site1,site2) both have the following configuration
[Code]....
from site1 i do
[Code]....
and in site2 if i checked if the user is authenticated ,i get a true, and i see "user1" as the current user.i know that what i have done above use a cookie,and as i know cookie are visible in the same domain (site) or sub domain,how form authentication make the cookie visible for both sites , this scenario must work for a site with two virtual directory inside it(sub site or application), but what is happening here any explanation.
we want all these requests to point back to www.site.com and not have to physically create the files and directories for every type of site... so if I just create a virtual directory (www.site.com/india) and point it to www.site.com... then I figure I can look at the URL and set some parameters/text/images accordingly to fill out the template
I went through the demo video and was able to create what little it showed but now I am wanting to extend it. I want to add an Admin section with a login page.
Can someone show me source code from an site that uses more than HomeController and multiple db tables calling stored procedures and such?
I want to make a page for registeration form. It will have name, address, gender, contact_no and email. User will key in data in the TextBox and all the data will save into the database after they click Submit button. I know how to design the UI and create database and table. But I didn't know how to save the value in the TextBox into the database.
We are working on a SharePoint Site where we have created lot of webparts. Now so far we have been creating SitePages for these webparts manually and adding webparts to those. It takes lot of time in any environment and its difficult to move from environment to environment.What is the ideal way of doing it? How can we automate sitePage creation process and hopefully add webpart to it by some scripts?
I try to construct a membership system using Walkthrough: Creating a Web Site with Membership and User Login. The membership system is going to be added to umbraco cms. I should admit that I am still in the learning process and need your guidance for my question.On my registration page other than standard fields which comes with CreateUserWizard, I need to add some extra fields in addition to that and those fields should be saved to database along with standard fields. Is it possible? If it is, how can I manage to do that?
I am having some trouble getting a second site to work with SSL in IIS 6. The server is Windows Server 2003 Service Pack 2.
I am getting the error "IIS was unable to start the site, Another site may already be using the port you configured for this site. Please select an unused port"
Both sites have different IP address but are on port 443.
When I stop one - I can start the other. But cannot run both at the same time.
I have tried editing MetaBase.xml file as a workaround but the file seems to be readonly. When I go to save, I get prompted to create a file.
I have custom redirection implemented in a module. Do I have to modify each config for all sites or is there a more general approach?Also, I have files in App_Data for this module, which would cause replication.
I'm currently in the process of creating a webshop. This webshop supports theming, but I also want customers to choose a lay-out. I can create multiple masterpages and create a handler to dynamically set the correct master page. But some components, like the shopping cart, are controls which have to be present in the master page and are also used in the aspx pages. The shopping cart control for instance, has an Update method which is called whenever the user adds a product to their cart. So the question is: can I somehow create a default masterpage which has all the components on it, but still be able to create multiple lay-outs. And how should I reference that master page from the aspx pages? I also thought of creating an Interface class which defines the masterpage and it's public components, but I don't know if I can reference an interface from aspx pages.
I'm trying to configure my Solution to publish multiple web sites to Azure using the 1.3 SDK and I want them to run under one Web Role. I've added the entry to the Sites element as per the CHM file and when I deploy to Azure the Instance starts up. Now for the symptoms:
Browsing to the "Primary" (first site added to the solution) everything works fine.
Browsing to the "Secondary" site throws the following error:
Exception type: ConfigurationErrorsException Exception message: Could not load file or assembly 'System.Web.Mvc, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (E:approot_WASR_1web.config line 28)
What have I tried so far without success (sigh):
1. I noticed that by default VStudio (2010 Ultimate) did not include the "Secondary" project output in the cspkg file. Setting a project dependency seems to have fixed that problem (or at least I now see it in the output window during the build process).
2. I've set "Copy Local=true" for the System.Web.Mvc on the "Secondary" project still nothing.
3. I have a CName setup for the "Secondary" project and use the hostHeader parameter on the Binding element so I haven't found a good way of testing this local so I'm limited in diagnostic info.
One thought that I had was that both projects now contain a WebRole.cs file, should that be the case in this configuration?
I work for a company that has many sites. Each site requires a login at some point. We have a single Accounts database that all of the sites hit.One of the requirements for the login system is that if we login on one site, we should automatically be logged in elsewhere.
The way it works right now is that on page load (or init, forget which) at any of our sites (let's say site1.com), it redirects to a "master" site (let's say sitemaster.com). On sitemaster.com there is a web service which checks to see if a cookie exists on sitemaster.com for that user. If it does, it redirects back and lets site1.com know that the user has already logged in (site1.com then creates a cookie for site1.com so we don't have to redirect to sitemaster.com in the future). If the user is not logged in at sitemaster.com, site1.com will then ask the user to login and, on submit, it redirects the user to sitemaster.com which logs them in, creates a cookie under sitemaster.com domain, redirects back to site1.com and lets site1.com know that the user is logged in (which then creates the cookie for site1.com).
On logout a similar method is employed.
Is this the best way of handling universal logins, or auto-logins across multiple sites? Is there a better way of doing things?
Some requirements:Most of our sites are in .NET 2.0, but there are plans to update them all to .NET 4.0. We want the best method for this auto-login system so if something requires .NET 4.0, that's ok.
The solution should not require javascript (our current solution requires javascript during the login process).The solution should not require Flash.It's ok to use iframes, as long as javascript is not requred.
We would like to be able to do AJAX logins (using jQuery) without having the site refresh. The current solution, due to the redirects, prevents us from doing that. (eg: Pop up a modal box asking the user to login, and when they do, the modal box disappears and some content is changed, but no site refresh required). This isn't absolutely necessary, but at the very least we should be able to verify a login using AJAX before any redirecting takes place.
I also have some questions related to the best way of re-using the auto-login code across sites (varying from ASP.NET 2.0 Forms to ASP.NET 4.0 MVC, but I'll save that for another question).
I recently inherited a solution with about 10 projects in it. 6 of these projects are individual websites that are basically copy/pastes of the original.
This means that any changes that need to be made must be made to each project in order to update all the websites.
What I want to do is have one project for the website code and be able to deploy that code and some configuration settings to create a new website. That way when I make updates to the main Web project I can just deploy to all the websites.
How do people normally approach this? I'll outline my thoughts on it and hopefully some of you can point out better ways to accomplish this or at least give me some affirmation that I am on the right track.
Have a master markup with very general containers. Allow the users/people setting up the site add widgets to the site which will be assigned to widget placeholders at the top and bottom of all the generic containers. All styling and colors will be controlled with a stylesheet that can be swapped out. I know there is some kind of theming you can do. Does this just swap out groups of css and let you configure which one to use in the webconfig? For elements that will be the same across all sites such as footer images have a naming convention. So if I want Site A to have some footer image I just replace the footer.jpg in the project when I deploy.
I'm planning to make a page that has about 10 different pages for varying use, for example, stats, data entry, reports, logistics, audit, sales, promo, etc etc. I'm anticipating there will be many combinations as to what pages a user may have access to, for each page, a user ought to be authorized to either enter new data, edit data, print and/or just view.
My questions are :
1. can membership & roles be used, once user is logged in, to display links to all the areas of the web app he is allowed access to?
[code]....
2. besides having access to a particular page, a user should, as mentioned before, be authorized to either enter new, edit, print and/or just view data. 3. Is there a preferred/better method to handle this besides using membership & roles?
I want to create several websites on my domain, and I am wondering how to go about this in MVC? Should I put them all within one project, and create separate folders in each Views, Models and Controllers folder for each site, or would it be better to create a separate project for each site, although I'm not sure how I would integrate
I have three asp.net 2.0 websites running on the same host server and recently upgraded to 3.5. After making changes necessary in the root web.config all sites run, but I've lost the stylesheet for the primary site.
Before the upgrade I had the following in the root web.config
<pages styleSheetTheme="Red" />
I got errors on this line because the upgraded web.config had another <pages> section. I tried adding the stylesheetTheme='Red" to that section and the primary website ran and looked right, but the subs got an error that there was no StyleSheetTheme="Red".
Each site has it's own stylesheets. How can I restore the stylesheettheme to the primary site without putting it in the root webconfig? Or, is there another way to handle this?
I have more of the same applications.All tables are identical.Each application has a new user.These different applications are located in different domains such as.: domena1.com, domena2.com, domena3.com.Each domain has different users.
For each domain in the web.config change the "ApplicationName", eg.: ApplicationName = domain1, ApplicationName = DOMAIN2, ApplicationName = domain3 ...
I have several ASP.NET sites in IIS7 and would like to be able to group them into folders (or other mechanism, if available). Ideally, I would use a customer name or account number and put the sites under there.
Is there a way to customize the organization of sites in IIS7, or is there just the one 'flat' view?
I am a new bie to work with ASP.net. I want to create an application /site in asp.net which work like content management system. As we see many sites are now a days being build on JOOMLA. How can we create such a CMS (content management system) sites using ASP.NET.
I have two websites that run on two different servers and they both both have their own asp membership databases. One is http:// and one is https://. Is it possible to create a way that a user can access both websites while only entering username and password once? Or if the user logs onto the https site can I then redirect to the http site and auto authenticate?
