soar_pl 0.0.2 → 0.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 0c29481be40d566195451c3e9bd78e080ab120a1
-  data.tar.gz: 2d98e776ca3c8f4953be65b021381b67e63b97b2
+  metadata.gz: a60e02f51f15f83466d5aa2ec75dca9a858b99dd
+  data.tar.gz: 371a9f475d7b5b8a903185a4e37053c469d0d127
 SHA512:
-  metadata.gz: af990036978a47d85e5dfe6216de6a05c50c22f5573771842f58c798dfababe8be2bd4738e288e37af9d05769cacc8779ab53b0c3f0c6c2cc201a10ed4298942
-  data.tar.gz: 66b001df7b86d41181299af9924e15a4a91a64cce487ab9c77b394d774771ff88ef115fd0504253ca772fa799d58ca3a27f248d3b73e9629c1732d3c1f024759
+  metadata.gz: 4062a881a1865fcf164864eb4fa73df635bbd87cf2d165f9d1ae17f10aedcd6c5384356c998e80d7e738c7f33d6f58e615a258b2eac2d1b6dcc636423885faa5
+  data.tar.gz: 215c8b4bfd84bd633309e67330d846bfe1e181adecc10c8c5ee145e24346eca3aff69a414fa27ce9141ebc0ee8830c1bef8e1c9b0654916c76d066c20dfd7a59

data/README.md

@@ -51,7 +51,7 @@ Optionally, require roles to be present for an entity that you identify with a s
 
     @iut.requires_roles(['client', 'owner'])
 
-If providing roles, you must provide an IDM to retrieve the entity's roles, and the attributes for each role, from:
+If requiring roles, you must provide an IDM to retrieve the entity's roles, and the attributes for each role, from:
 
     @iut.has_idm(@idm_instance)
 
@@ -67,7 +67,7 @@ The result is jsend of the form:
 
 The result status will be 'fail' if something goes wrong, such as a validation failure. The status will be 'success' if the authorization took place, regardless of a true or false value for 'allowed'. 
 
-When building your rule set, you can use both your configuration as well as the parameters passed to the authorize method, and roles and attributes obtained from the IDM. You only have to override the apply_rule_set method as below. By the time apply_rule_set is called, you can rest assured that all required roles have been checked, if you specified an IDM. IDM failures result in an Entity error being reported. E.g.:
+When building your rule set, you can use your configuration as well as the parameters passed to the authorize method, and roles and attributes obtained from the IDM. You only have to override the apply_rule_set method as below. By the time apply_rule_set is called, you can rest assured that all required roles have been checked, if you specified an IDM. apply_rule_set must return a boolean indicator and a string message, e.g.:
 
     require 'soar_pl'
 
@@ -79,6 +79,8 @@ When building your rule set, you can use both your configuration as well as the
       end
     end
 
+IDM failures result in an Entity error being reported.
+
 ## Deploying
 
 This authorization policy framework can be deployed in-process in any ruby application or application server. It was intended for the SOAR architecture and to be deployed on soar_sc service components.

data/lib/soar_pl/version.rb

@@ -1,3 +1,3 @@
 module SoarPl
-  VERSION = "0.0.2"
+  VERSION = "0.0.3"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: soar_pl
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 0.0.3
 platform: ruby
 authors:
 - Ernst van Graan