Skip to content →


  1. Holy shit, I finally looked at the tetheredtothesun gallery today, and I was blown away. I’ve just been getting into Terry Richardson’s stuff lately, but this is far more personal and emotional as far as gonzo photography goes.

  2. A quite intrestingidea is realized in this website! And a good and easy to handle design has been found too!

  3. Every so often, when we’re lucky, widespread necessity and solution maturity collide head-on. This is exactly what’s happening today in the sphere of identity management. Although the underlying concepts of identity management aren’t new, it’s becoming clear that the execution of these concepts by solutions vendors is ready for the mainstream.

  4. Between mandates from on high, such as Sarbanes-Oxley, and needs from below, such as the need to address management headaches associated with the constant march of new applications into the core infrastructure, the time of managing disparate systems and applications in silos is necessarily drawing to a close.

  5. Bringing disparate systems together for centralized user provisioning and access management is a significant challenge, as our testing showed, but it’s more than possible — it’s inevitable. Automating your infrastructure by implementing an identity management solution is likely to be the largest IT project you’ll undertake for years to come, but it also has the potential to be the most rewarding. The potential calm after the storm is not to be overstated.

  6. Sun Identity Manager seemed the most mature overall, with strong integration and management capabilities, but still lacks the reporting and front-end polish we were expecting. IBM and Courion have similar work to do on the manageability front. Indeed, Courion needs to keep working on making the flexibility of its solution more accessible. Novell has paid much attention to its front-end tools, producing the easiest solution to configure and manage by far, but it still needs work on the back end to match the depth of Courion or Thor. Finally, Thor was strong from stem to stern, although their implementation process required a good share of custom coding as well.

  7. Identity credentials have contexts. Consider, for example, a Government issued passport and a coffee club card. The context for the passport is a border crossing. The context for the coffee club card is buying coffee

  8. As an example, you might use a credit card to pay for your purchase at the coffee shop and be asked to present some kind of identity credential. In that case, using your passport at the coffee shop would be out of context, but you’d be doing so because the coffee shop cashier is willing to recognize your passport as a means of establishing your identity.

  9. The recent move by the Utah Legislature to issue driving privilege cards (DPC) instead of driver’s licenses to illegal aliens belies that. Issuing a DPC sends the message, loud and clear, that the driver’s license is an identity document that is frequently used out of its original context. Of course, as a private citizen, you’re free to recognize the DPC as an identity document if you like. I suspect, for example, that it will be readily accepted as proof of age by convenience stores that want to sell beer and cigarettes. That kind of out of context use will continue

  10. But, the legislature specifically ruled out its use in certain contexts. For example, the DPC cannot be used to identify yourself when you fly. Nor can it be used to claim certain government benefits. Getting a driver’s license opens the door to all kinds of opportunities in our country. The intent is that the DPC will not.

  11. The term trust carries an enormous amount of baggage, so it would be better if we could understand what’s happening without relying on it. When we speak of trust in the context of digital identity, we’re really talking about surety and risk management. Gaining trust in another entity is the process of gathering evidence that can be used to estimate the level of risk for a transaction. Let’s use that concept to work through the coffee shop scenario without using the word “trust.”

  12. The clerk asks to see a form of ID (a credential) along with the credit card to reduce the risk of fraud. The clerk expects that you will produce a credential that is easily authenticated. Moreover, the clerk will evaluate the risk based upon his perception of the level of care the issuing organization has taken to vet the person, his familiarity with the organization, and how difficult the credential is to fake.

Comments are closed.