There are several reasons… you need an identity so that the service provider is able to uniquely identify you and provide the right level of service. You need an identity so that the systems can provide access to your information only. You need an identity so that the system can provide you the privileges you are entitled to. I can keep adding, but you get the picture... Blog Post by: Benny Mathew

The most common and still widely used method of representing / establishing identity in the digital world is through UserName and Password. Although there are other forms such as Biometrics (Fingerprints, Iris Scan, etc.), Digital Signatures / Tokens, Smartcards etc. Blog Post by: Benny Mathew

Think of it as a set of characteristics or attributes of an individual entity (person, object etc.) that are distinct and persistent and could be used to differentiate it from other (similar) entities. In layman’s language it is what makes a person or a thing unique and different from the others. Blog Post by: Benny Mathew

After a long period of inactivity, decided to get active again on the blogosphere. This time however, it’s not (just) going to be on BizTalk , (I’ve lately been through some “Identity crisis”… so) you will see me talking about how to protect your identity, get help through “Identity Federation”, asserting your identity, using “Proxies” etc. Also thought of creating a new Identity for myself here , instead of trying to regain my lost identity...

This morning while reviewing sample code I ran across the collection activities.  Working with these activities is fairly straightforward but there are some issues that you should be aware of that can impact the behavior of your workflow. These issues are familiar to .Net developers because they impact the basics of object equivalence and how the collection classes behave. However many workflow developers are building workflow activities that are meant to be used by non-developers. For this...