Search Results for "p-unit"

...Extend them however you need with Oso’s declarative policy language, Polar. Filter: Go beyond yes/no authorization questions. Implement authorization over collections too - e.g., “Show me only the records that Juno can see.” Test: Write unit tests over your authorization logic now that you have a single interface for it. Use the debugger or tracing to track down unexpected behavior. Oso lets you write policies to control who can do what in your app. Select different policies below to see how they change the permissions in the sample app on the right. Oso's language libraries can be developed without touching the Rust core, but you will still need the Rust stable toolchain installed in order to build the core.

...In order to specify security-related context information, SEWOL provides access control models such as access control lists (ACL) and role-based access control models (RBAC). SEWOL uses and encloses the following libraries: - TOVAL (http://sourceforge.net/p/toval), - JAGAL (http://sourceforge.net/p/jagal), - OpenXES (http://www.xes-standard.org/openxes/), - Spex (http://code.deckfour.org/Spex/) - Google Guava (https://github.com/google/guava), - xstream (http://xstream.codehaus.org/) and - graph-impl and visualization components of Jung 2 (http://jung.sourceforge.net/). Documentation: http://doku.telematik.uni-freiburg.de/sewol

RBAC (role based access control) is the de-facto standard in authorization and access control, because its much easier to maintain and use than traditional ACLs. Unfortunately due to its complicated internals, not many implementations are available. PHP RBAC is compatible with NIST Level 2 RBAC standard and provides even more, with best performance yet available for any authorization library, and its for PHP. Note: Development and support has been moved to Github...