We are happy to announce that Shiro is now integrated with release 1.2 of Cibet <http://www.logitags.com/cibet> . With Cibet there are much more flexible configuration possibilities for access rules. Here are some examples of what can be done with Cibet that can't be done with stand-alone Shiro: define permissions dependent on any business logic with JavaScript. Example: define different access rules dependent on the state of the user support of dual control mechanisms (context awareness): Allowing a method invocation under 4-Eyes to one group of users and the release to another group while a redo of the same method invocation to a third group. grant access dependent on date and time. Example: restrict execution of payments to working hours between 9 to 5. define dynamic permission rules by configuration. Permission rules can be changed without redeployment or restarting of the application. define persistence rules for domain objects. Example: grant deletion of customer objects to a special user group restrict update of domain objects depending on the data which are modified. Example: deny update of a customer when his bank account number changes and assign this right to a special group apply different access rules dependent on the technical caller. Example: define different access rules for a method if called from administration GUI, call center GUI, web service, batch process or dependent on IP define different access rules dependent on the client (tenant) in a multi-client system
-- View this message in context: http://shiro-user.582556.n2.nabble.com/Enhance-Shiro-functionality-with-Cibet-tp7578000.html Sent from the Shiro User mailing list archive at Nabble.com.
