I talk to a lot of people regarding Identity Management solutions in my position at Sun. Inevitably, during conversations there are terms which it becomes clear are not mutually understood by both parties as the same meaning. Usually when this happens, some time is spent describing "what do you mean by" xxxxx. Here are a few examples of some terminology overloading just in the Sun Identity Product portfolio (Sun Java System Directory Server, Sun Java System Access Manager, and Sun Java System Identity Manager): Role, Policy, Schema. This list is by no means comprehensive. There are of course many more terms, but these terms seem to be the ones which cause contention the most often.

The purpose of this entry is simply to demonstrate that seemingly simple terms can have different meaning in different contexts. A quick search on Wikipedia reveals a commonly accepted definition of these terms. Below I attempt a simple correlation to the Wikiepedia term and it's context in the Sun Identity products.:

Policy

Wikipedia Entry: A policy is a plan of action to guide decisions and actions. The term may apply to government, private sector organizations and groups, and individuals. The policy process includes the identification of different alternatives, such as programs or spending priorities, and choosing among them on the basis of the impact they will have. Policies in short can be understood as political, management, financial, and administrative mechanisms arranged to reach explicit goals.

Sun Product Use of this term:

Role

Wikipedia Entry: A role (sometimes spelled rôle) or a social role is a set of connected behaviours, rights and obligations as conceptualised by actors in a social situation. It is mostly defined as an expected behaviour in a given individual social status and social position.

Sun Product Use of this term:
  • Sun Java System Access Manager: Access Manager Role (static or filtered) - A filtered role is a dynamic role created through the use of an LDAP filter.
  • Sun Java System Directory Server: Directory Server Role - Roles are defined and administered like groups, but they provide more efficient grouping mechanisms for applications. Roles can be used in ACIs to control access to data.
  • Sun Java System Identity Manager: Provisioning Role: A grouping of users which is primarily used to determine indirect provisioning operations. This includes which accounts to create for a user as well as what role based attributes to provision for the user. This includes the ability to create accounts in a specific order, and assign role approvers during provisioning
  • Sun Java System Identity Manager: Administrative Role: A grouping of users which is used to assign delegated administration capabilities (what a administrator can do, ex: reset password) to an administrative user of the provisioning system.

Schema

Wikipedia Entry: A schema in general is a specific, well-documented, and consistent plan. The related word, scheme means a loosely described plan. The word schema comes from the Greek word "σχήμα" (skhēma), which means shape or more generally plan.

Sun Product Use of this term:
  • XML schema: XML Schemas express shared vocabularies and allow machines to carry out rules made by people. This pertains to all 3 products in various places
  • Sun Java System Access Manager
  • Sun Java System Directory Server: An LDAP directory server uses schema to describe the object models which is used to store entries. Objectclasses are defined which include attributes (required and allowed). The type (string, integer, whether it can be multi-valued, etc.) of each attribute is also stored in the schema.
  • Sun Java System Identity Manager: Database Schema - Identity Manager uses a database repository as part of installing the product the database schema must be imported.
  • Sun Java System Identity Manager: Identity Manager uses agentless Resource Adapters to provision user accounts. Each Resource Adapter uses a schema to map attributes associated with a user to attributes which the provisioning system understands
  • Sun Java System Identity Manager: Service Provisioning Markup Language (SPML) Schema - SPML uses a schema to map incoming SPML attributes (typically associated with a user) to attributes which the provisioning system understands


Comments:

Add to the confusion the fact that the owners of the various system resources that Identity Manager connects to for provisioning purposes have their own notions and definitions of security-related terms based on how those systems operate. It's no wonder that it takes a lot of time to get everyone on the same page. Maybe the various product lines across Sun that are closely related to each other should standardize on common terminology and definitions for documentation and marketing information?

Posted by Rene Ugarte in Content Management on December 16, 2006 at 03:16 PM CST #

Derrick, I understand your issue, and it's useful to see a systematic breakdown of where the confusion arises. To some extent, though, even a clear taxonomy based on your findings wouldn't fix the problem, and here's one reason why:

The confusion doesn't just arise out of semantic overload... it also arises from the fact that the same string of bits is legitimately interpreted in very different ways depending on which component is interpeting it.

Here's an example The same string of bits is interpreted by an XML parser as 'a message'; a Liberty endpoint as 'an assertion'; and a business application as 'an expression of warranty'.

They're all correct interpretations - but that implies that the same string has a least three different 'meanings'...

Posted by Robin Wilton on December 16, 2006 at 05:06 PM CST #

I could not agree more. I am not trying to recommend a simple solution to this issue, rather just identifying it as a recurring theme in my identity conversations over the years, which seem to be more and more repetitive lately (perhaps because Sun solutions are commonly including a more diverse mix of products).

I admittedly only scratch the surface of this issue since I only look at it from a Sun product perspective. The more important perspective may be from the customer perspective which includes their business requirements as well as their current infrastructure and installed products. First to understand their requirements, then to map a Sun solution (which may contain many products) to meet their requirements.

Thanks for the comment!

Posted by Derrick Harcey on December 17, 2006 at 09:19 AM CST #

Post a Comment:
Comments are closed for this entry.

This blog copyright 2009 by harcey