during web site design stage or when web site is running on production server?
If it's used then it's during design stage to make some settings, create (test) users and roles and mix these two together.
Personally I don't really use it during development for customers as these applications mostly have to integrate with a legacy users database or something else like NAM. For these I simply create custom membership and role providers, plug them in, works.
If you are building an asp.net site from scratch its a very useful tool to expedite your development process.
It can create an authentication system for you that ties directly into the login control available in visual studio.
I find it particularly useful for creating and configuring the .NET Roles and Membership tables.
Related
Now that Microsoft has removed support for the ASP.NET Web Application Management tool in Visual Studio 2013, what is the best way to manage users and roles in your ASP.NET applications?
I'm starting on a new web app, and instead of building my own system for authentication and role management, I planned on using ASP.NET. However, what is the easiest way to add roles and members without directly editing the database?
I would suggest following the methodology used in the ASP.NET Identity Sample:
https://github.com/rustd/AspnetIdentitySample/tree/master/AspnetIdentitySample/Controllers
They use two Controllers: RolesAdminController and UserAdminController.
Using this scheme would allow for a seeded administrative account to then manage the roles and users of that site.
I suspect you could probably just copy those straight into a new project using the new Identity scheme with very few modifications to work properly. However, I haven't personally attempted doing that part myself.
I'd like to make an OOB Silverlight app based on the Silverlight Business Application template in Visual Studio. The template uses the default ASP.Net membership provider. I understand how to use that to add users and roles, etc. I've found plenty of tutorials on that. What I'd like to be able to do, is configure the Silverlight template so that it uses an existing ASP.Net membership base. We'd like this app to have a companion website (ASP.Net based).
To clarify: We've been able to setup an ASP.Net website and have created a SQL database with the required tables (aspnet_Users, aspnet_Membership, etc.). I'd like to configure a Silverlight app to access the same users and roles that are in those tables.
Can anyone help me out in terms of what I'd need to put in the Web.config? Do I just need a connection string? I'm new to ASP.Net authentication, but I'd rather use what ASP.Net gives me out of the box than have to write my own authentication service. I feel like this should be really easy, and is just a matter of pointing the Silverlight app in the right direction.
I'd like to use Silverlight 5 and .Net 4.5 if I can but I don't mind using an older version of either if it makes things easier.
You can just point the connection string to the existing database.
From this answer:
You can point your connection string for authentication to a database that all application can access.
So if you have the default database that .NET creates, you can point your other application to that as well for authentication.
i have existing asp.net web application it includes membership and roles and admin section,etc. Now i would like to integrate dotnetnuke journal module in my asp.net web application.
is it posible to integrate dotnetnuke module in my web app? i download dotnetnuke source and i compiled journal module.
can any one update me how to integrate dotnetnuke module in my web app..i don't want to switch to dotnetnuke for now.
Your best bet would be to utilize the APIs to access the journal from your custom application.
The module itself is dependent upon DNN and its context (users, pages, modules, etc) in order to function properly.
I am sure you could rip a lot of that out, but I am not exactly sure what you are trying to do.
is it posible to integrate dotnetnuke module in my web app?
No.
Your only way to succeed in your quest would be to convert your ASP.NET application into the DotNetNuke application. To do that, you're going to have to merge the authentication side of the two sites. This shouldn't be impossible since DNN uses the ASP.NET authentication provider.
If you can merge the user database into a DotNetNuke installation properly, you're halfway there. You could then use the DotNetNuke page management features to load your custom pages by linking to them directly, and gradually merge your existing application.
Otherwise, you have no hope of integrating the Journal module. And you're up for hundreds if not thousands of hours of coding to try and replicate it.
I have a LightSwitch customer-order management application. The customers can login and only view their orders. I'm trying to create a similar web app but not sure what route to take - ASP.net...etc. since not all my clients have Silverlight installed. If I did this in ASP.NET with Visual Web Developer, how would I go about the authentication based on the customer record in the db? It wasn't as big of a deal in LightSwitch.
There is an article on Codeproject about sharing the authentication between a .NET app and LightSwitch. Basically it comes down to 2 things in the web.config; MachineKey, and Forms Cookie. These have to be the same in all web.config files, and it automatically works.
http://www.codeproject.com/KB/silverlight/DNNThingsForSale.aspx
Also, Team Foundation Server has a web front end, and it exactly represents what is in the application.... Team Foundation Server uses the exact same way of describing the UI as LightSwitch ... so you might find something there.
I have a website that uses ASP .Net membership and roles using the SqlMembershipProvider and SqlRoleProvider. Right now I am only using this for a small section of the site that only 2 people have access to. The site may expand in the near future and the number of users could grow into the thousands.
My question is, is there any kind of open source administration tool for managing users or am I stuck building my own? I can't really use the ASP .Net Web Application Administration Tool because, as far as I know, it is only accessible from Visual Studio. User administration would be handled by our help desk and would need to handle all of the things that the stored procedures in the SQL server provide such as adding users on the customer's behalf, resetting passwords, unlocking users, etc.
I just can't believe that an administration front-end has not been developed to handle these sorts of things and provide more functionality than the ASP .Net Configuration page provides.
Take a look at MyWSAT on CodePlex.
http://mywsat.codeplex.com/
MyWSAT aka ASP.NET WSAT is a WebForms based Website Starter Kit for the ASP.NET Membership Provider with Forms Authentication. It provides you with all the security features required for a site out of the box so you start focusing on building your pages. It allows you to manage membership users online once your site is deployed. It features complete administrative back-end functionality and designed to manage users, as well as admin pages for users to manage their own user data.