> On Dec 8, 2015, at 8:58 AM, Boris Bobrov <[email protected]> wrote: > > I'm trying to understand how the XML I'm sending to the Fortress REST API > should look like. So far I've experimented with test files in > fortress-enmasse/src/test/resources/ > and them seem to be working. But how do I understand which parameteres > are required for userGrant call? There are several fields in > emTestCheckAccess.xml, where do they come from? > > A similar question was answered in [0], but I still can't figure it out > > [0] https://www.mail-archive.com/[email protected]/msg00041.html > > As a general note, it would be very valuable to have docs for non-Java people, > especially because the REST interface will be used mainly by them.
Hello Boris, Probably the best place to go to determine what the required and optional attributes are is the generated javadoc. Here is an older copy: http://symas.com/javadocs/enmasse/ For example the grant service: • grant org.openldap.fortress.rest.FortResponse grant(org.openldap.fortress.rest.FortRequest request) This command grants a role the permission to perform an operation on an object to a role. The command is implemented by granting permission by setting the access control list of the object involved. The command is valid if and only if the pair (operation, object) represents a permission, and the role is a member of the ROLES data set. required parameters • FortRequest.entity - contains a reference to PermGrant entity PermGrant required parameters • PermGrant.objName - contains the object name • PermGrant.opName - contains the operation name • PermGrant.roleNm - contains the role name PermGrant optional parameters • PermGrant.objId - contains the object id optional parameters • FortRequest.session - contains a reference to administrative session and if included service will enforce ARBAC constraints Parameters: request - contains a reference to FortRequest Returns: reference to FortResponse
