scalable/reusable authorisation model


ok, i'm looking bit settlement guidance, organisation removing luck re-cast certain decisions new underline we're building, i wanted guess :-) there impetus certain things we're changing, fortitude have fit model. namely, we've got an asp.net application, uses web services grant users perform actions system.



the problem comes because, systems, opposite users need opening opposite functions. roles have opening y button, others have opening y b button, while another still wholly opening b. many i this, developers only put mish-mosh statements understanding ui state. fear left unchecked, spin an unmaintainable mess, since offer putting authorisation explanation gui, needs put web services (which called around ajax) pledge wholly certified users certain methods.



so doubt is, component designed diminution futile ad-hoc statements here there check specific roles, re-used both gui/webform code, web use code.



just clarity, an asp.net web application, controlling webforms, ajax functionality. don't let script# pitch off answering, it's essentially opposite asp.net ajax :-)



Comments

Popular posts from this blog

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?

grails record upload problems

how i emanate permitted url asp.net mvc?