roles

i have a project using ASP.Net MVC3 and using membership for roles. i use authorize in every controller. eg: [Authorize(Roles = "Administrator")] public ActionResult Index(string q, int i) { return View(model); } if someone doesnt have role for administrator, then it will redirect to login page by default. how to change it,so it will redirect into Views/Shared/UnAuthorize.cshtml ? or maybe if someone doesnt have role for administrator, it will show message box (alert) ? thanks in advance. Just change the page that have to be shown in the web.config (check that the route exists) <authentication

How do I write an SQL script to create a ROLE in PostgreSQL 9.1, but without raising an error if it already exists? The current script simply has: CREATE ROLE my_user LOGIN PASSWORD 'my_password'; This fails if the user already exists. I'd like something like: IF NOT EXISTS (SELECT * FROM pg_user WHERE username = 'my_user') BEGIN CREATE ROLE my_user LOGIN PASSWORD 'my_password'; END; ... but that doesn't work - IF doesn't seem to be supported in plain SQL. I have a batch file that creates a PostgreSQL 9.1 database, role and a few other things. It calls psql.exe, passing in the name of an SQL

I currently have a project that I seem to have ran into an issue regarding Roles and thought I would get some opinions on how to best handle the problem. The system will require editable, flexible roles that control not only the access of specific areas, but also the use of system functions (Adding Users, Editing Users, Viewing Reports etc.) The system currently allows users to have multiple roles, each of those roles has explicitly defined areas of access/actions, for example: Role A can access areas 1,2,3 and can Add Users. Role B can access areas 1,5,7 and can Modify Users. Role C can

I am completely new to the use of claims in ASP.NETIdentity and want to get an idea of best practices in the use of Roles and/or Claims . After all this reading, I still have questions like... Q: Do we no longer use Roles? Q: If so, why are Roles still offered? Q: Should we only use Claims? Q: Should we use Roles & Claims together? My initial thought is that we "should" use them together. I see Claims as sub-categories to the Roles they support. FOR EXAMPLE: Role: Accounting Claims : CanUpdateLedger, CanOnlyReadLedger, CanDeleteFromLedger Q: Are they intended to be mutually exclusive? Q: Or is

How do I set the role prefix to "" with a custom user details service in Spring? <beans:bean id="authService" class="com.cisco.badges.business.services.AuthenticationService"/> <authentication-manager> <authentication-provider user-service-ref="authService"> <password-encoder ref="passwordEncoder"> <salt-source ref="saltSource" /> </password-encoder> </authentication-provider> </authentication-manager> @Service("authService") public class AuthenticationService extends BaseService implements UserDetailsService, IAuthenticationService { @Autowired IUserRepository userRepository; @Autowired

I am trying to implement basic role management manually. When a user logs in if they are admin or not they are added to a role I am getting this error: Exception Details: System.Configuration.Provider.ProviderException: The Role Manager feature has not been enabled. This is the method that causes the error: public void addUserToRole(String user, String role) { if (!Roles.RoleExists(role)) Roles.CreateRole(role); Roles.AddUserToRole(user, role); } here is my web.config <profile defaultProvider="DefaultProfileProvider"> <providers> <add name="DefaultProfileProvider" type="System.Web.Providers

I have a stored procedure that finds all the existing databases and reads from a table in each one. Is there a way I can give a login read access to all databases, and to all future databases i.e., I won't have to do anything when a new database is added? Is there a server role that would work? Is there a way to make a SQL agent job add the permissions on any new databases? Or is there some other method? For new databases, add the user in the model database. This is used as the template for all new databases. USE model CREATE USER ... FROM LOGIN... EXEC sp_addrolemember 'db_datareader', '...'