There has been some discussion on the idworkshop list about defining an identity stack, on the premise that it would help clarify the discussion similiar to how the 7 layers of networking provided clarity. (I was not around at the time, so don’t know first hand if it helped 🙂

It reminded me of some brainstorming we had done here at Sxip — so I’ll toss out these 4 layers of identity:

4. asserted identity


3. entity identity


2. profile identity


1. session identity

  1. Session identity is knowing it is the same the same entity throughout a session. Cookies are often used to track this in web applications.
  2. Profile identity is user asserted data about themselves such as postal address, favorite colour, photo etc.
  3. Entity identity is knowing it is the same entity across sessions, and perhaps even across servers. Providing the same username/password can provide entity identity. A URL provided by OpenID does a similar task.
  4. Asserted identity is where a trusted 3rd party makes a statement about the entity or session. This could be that the user is an employee of a company, is over 21, is Star Alliance Gold, has an email address etc.

Does this make sense or am I smoking crack?

Update

Discussion on the gang list has moved to agreeing that the concept of a “stack” or a “layers” is likely not the right way of looking at the problem. An architecture may be a better approach. Stay tuned.