I’m building a dynamic navigation control which toggles the visiblity of elements in the navigation depending on which pages the user is authorized to view in the web.config.
We’re beginning to design a whole bunch of new services to create (WCF, ADO.NET Data Services, possibly in the cloud at some point) and one question that pops up is what authentication and authorization scheme to use – there are quite a few!
I m working on ASP.NET MVC 4 application.I have a dashboard and my users groups will be based on Windows Domain
So I am using WIndows Authentication for authenticating users.
I created sample applications which uses custom authentication by overrides functions AuthorizeAttribute, ActionFilterAttribute . Is this a good approach ?
I am building a web application using ASP.NET MVC that has two very distinct types of users. I’ll contrive an example and say that one type is content producers (publishers) and another is content consumers (subscribers).
In the DB i have Role and User entities with one to many relationship.
I’m making a simple website that lists files from a certain folder. If the user has admin rights, the user can delete files by clicking the “Delete” button.
I run an Azure web role in Full IIS mode. Requests are authorized with custom basic authentication.
In .NET WebAPI, I’ve created a way to have all of the authorization rules in a central location, rather than scattered throughout controllers. I’m curious why this centralization isn’t done more often; are there repercussions/security concerns?
Every bit of research on this topic is showing how to do this tasks with MVC, my project is MVP webforms based. I have the authentication done, but is there a pattern or strategy to best do authorization?
I have an ASP.NET (v2.0) web application that uses a reference to a SQL Server Reporting Services 208 R2 instance (using the ReportService2010.asmx service endpoint). The web application is hosted on ServerA and the Reporting Services instance is hosted on ServerB. ServerA is running Windows Server 2003 (IIS6) and ServerB is running Windows Server 2008 R2.