Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Stardust/Knowledge Base/Java API/Document Security

< Stardust‎ | Knowledge Base‎ | Java API
Revision as of 05:27, 13 March 2012 by Ganesh.lawande.sungard.com (Talk | contribs) (Updating the Document Security:)

Overview:

Stardust comes with built in Apache’s Jackrabbit, an open source JCR implementation. Stardust provides a service, called Document Management Service (DMS), to integrate with JCR. Apart from document CRUD, it integrates well with Stardust users, roles, departments, and process attachments seamlessly.

In this article, we will see basic document security API features available with the Stardust. Admin can control the security settings using document repository view of the Stardust portal. For detail, refer “Infinity Documentation > End User Handbooks > Infinity Portal > Common Detail Views and Dialogs > Access Control Editor” section of product documentation at https://infinity.sungard.com/documentation/ipp/6.0/index.jsp


Enabling Document Security:

Document security is not enabled by default. Refer the product documentation mentioned above for enabling document security.

Document Management Service:

This service, DMS, provides the basic API for documents and its security management. It provides the features to create, read, update, and delete the documents and folders. <methods used to get and set policies>

In the next, we will see how we can read and update the security associated with the documents.


Security Data Structure:

A document has set of AccessControlPolicy objects containing security permissions associated with it. Each AccessControlPolicy has a set of AccessControlEntry objects. Where, a signle AccessControlEntry object represents a principal along with its security fields, called privileges.

A principal can be any model participant or dynamic/runtime entity like user or department. The set of privileges can contain all or subset of security permissions given below.


ACL Security Fields:

The document security has the following six fields:

  • Create
  • Read
  • Modify
  • Delete
  • Read ACL
  • Modify ACL

All of these fields can have value of “Allow” or “Deny” to indicate the corresponding permissions. These fields are editable per participant. Any number of available participants can be added on the document ACL and thus their security permissions can be edited separately.


Reading the Document Security:

The following code snippets show how to read the security data associated with the sample document;


== Updating the Document Security: ==

The following code snippets show how to update the security data associated with the sample document;

<code goes in here>


== Summary: ==

Back to the top