The JSON Schema Behind the Entitlements Service
What better day than Friday the 13th to write about the JavaScript Object Notation (JSON) schema used by the Entitlements Service to write the privilege objects returned by Those Darlin'OpenSSO REST Policy Evaluation Interfaces. JSON is relatively easy to read and understand. According to Introducing JSON, it is easy for machines to parse and generate...and is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language. (Check out the link for more information.)
An Entitlements Service privilege object has the following attributes:descriptionis a descriptive string.entitlementis made up of:
- name (any arbitrary unique String)
- application name
- set of action values (String to boolean)
- list of resource names
- a list of exclusive resource names
subjectscan include one or more entitlement subjects; in that case, logical subjects such asOrSubjectandAndSubjectare used. Please refer to sub section, Sub ject JSON Representation for schema for the support sub jects.conditionscan include one or more conditions; in that case, logical conditions such asOrConditionandAndConditionare used. Please refer to sub section, Condition JSON Representation for schema for the support conditions.attributesmay include user and static attributes.
Posted at 08:40AM Nov 13, 2009 by Michael Teger in Sun | Comments[0]
