OPA for HTTP Authorization

Open Policy Agent[1] is a promising, light weight and very generic policy engine to govern authorization is any type of domain. I found this comparion[2] very attractive in evaluating OPA for a project I am currently working on, where they demonstrate how OPA can cater same functionality defined in RBAC, RBAC with Seperation of Duty, ABAC and XACML.  
Here are the steps to a brief demonstration of OPA used for HTTP API authorization based on the sample [3], taking it another level up.
Running OPA Server First we need to download OPA from [4], based on the operating system we are running on.  For linux, curl -L -o opa https://github.com/open-policy-agent/opa/releases/download/v0.10.3/opa_linux_amd64 Make it executable, chmod 755 ./opa Once done, we can start OPA policy engine as a server.
./opa run --server Define Data and Rules Next we need to load data and authorization rules to the server, so it can make decisions. OPA defines these in files in the format of .rego. Below is a sample …

Documentation-patch submission for Apache issues

Submitting a patch for a documentation issue is same as submitting a patch for a code issue. Only thing to be noticed is where the source code for sites resides. Here I am sharing the steps in a very basic level as helpful for a beginner, from identifying an issue to the submission of patch.

Note:The sample commands I am using here are for linux and for other environments the relevant commands should be applied for same functionality.
  • After identifying the issue from Apache issue navigator, check out the relevant files directory from apache SVN. 
  • Navigate to the relevant .xml files and do the improvements or corrections needed and make sure the xml validation is done and the document is presented as it is intended to be. 
  • Lets see how the changes are applying. In the top level directory that includes all the changes and improvements enter the following command. 

eg : svn co http://svn.apache.org/repos/asf/axis/axis2/java/core/trunk/src/site/xdoc/

eg: svn diff -x-p

You will see something as follows,



- lines preceded with - are to be deleted

- lines preceded with + are to be added

Make sure those are the intended changes and then create the patch with the following command:
Now submit the patch at the jira issue page as follows and add any meaningful comments.

svn diff ><the preferred name for patch file>

eg: svn diff >AXIS2-4655.patch




Keep in touch for updates on the patch submitted. Keep contributing.

Comments

  1. Thank you for providing this resource to the web.
    Review my web site - Belleville Washers

    ReplyDelete
  2. Thanks! This article was very helpful and saved me many hours of digging and experimentation.

    ReplyDelete

Post a Comment

Popular posts from this blog

Signing SOAP Messages - Generation of Enveloped XML Signatures

How to send an HTML email in Java (Using Google SMTP Server)

How to convert WSDL to Java