|
On 05/05/2014 03:40 AM,
Andrea.Vicentini@t-systems.com wrote:
Fortress refers to a family of products, each implement the RBAC specification but perform a different function. 1. Fortress Core - Java APIs that implement ANSI RBAC functional specs for: a. System Operations - Runtime access control: createSession, checkAccess, addActiveRole, etc... b. Administrative Operations - Setup: addUser, addRole, addPermission, updateUser, updateRole, etc... c. Review Operations - Policy interrogation: assignedUsers, assignedRoles, userPermissions, userRoles, etc... 2. Fortress Commander - RBAC Web admin that drives (depends on) APIs of #1b & #1c - deploys inside Java servlet container as a Java web app 3. Fortress EnMasse - a RESTful interface that drives (depends on) the APIs in #1 - also deploys in Java servlet container - non-Java clients use EnMasse for #1a,b,c. 4. Fortress Sentry - Policy Enforcement Points (PEP) that drive (depends on) APIs in #1a. - PEP plug-ins for Tomcat, JBoss and Websphere to perform authentication and authorization for Java web apps 5. Fortress Accelerator Client - uses LDAPv3 extended controls to communicate with the RBAC Accelerator Server for execution of RBAC system APIs - The RBAC accelerator 'server' is a new OpenLDAP overlay - Java bindings released - C bindings have been coded, but not released - Python bindings are in planning stage On 05/05/2014 03:40 AM,
Andrea.Vicentini@t-systems.com wrote:
And what is the status of the RBAC submission? Can you clarify - are you referring to the standard RBAC schema for directory servers? -- Shawn McKinney shawn.mckinney@jts.us |