There has been a great deal of excitement about the US Federal Government's ICAM initiative that provides for the development of Trust Frameworks, and providers of same, that has resulted in the emergence of identity providers who can issue credentials to citizens that can be used to gain access to Government websites/applications/relying parties. In all of the discussions surrounding these efforts, the focus has been on leveraging existing OpenID, Information Card or other types of credentials issued by commercial or educational organizations to access Government resources.

But, is that all we want from our Government?

In this blog posting, I am going to consciously side-step the concept of the Government as an Identity Provider. In the United States at least, much more thoughtful people than I have discussed, debated and argued about the feasibility of this and I do not believe that I can add much value here. The general consensus to date seems to be that the value proposition around the concept of a "National Identity Card" has many challenges to overcome before it is seen as something that is viable in the US. Whether this is true or not, I leave to others to ponder.

But what about the US Government vouching for the attributes/claims of a person that they are already managing with our implicit or explicit permission?

My last blog post "The Future of Identity Management is...Now" spoke to the pull-based future of identity management:

• ...
• "The input to these decisions are based on information about the subject, information about the resource, environmental/contextual information, and more, that are often expressed as attributes/claims.
• These attributes/claims can reside in multiple authoritative sources where the authoritative-ness/relevance may be based on the closeness of a relationship that the keeper/data-steward of the source has with the subject."
• ...

There are certainly attributes/claims for which the US Government has the closest of relationship with its citizens and residents and as such remain the authoritative source:

• Citizenship - State Department
• Address Information - Postal Service
• Eligibility to Work in the US - Department of Homeland Security
• Eligibility to Drive - State Government DMVs
• More...

I may be wrong about which agency is responsible for what, but I hope you see my point. There are some fundamental attributes about a person, that in the US, that are managed through its life-cyle by the Government, whether Federal or State.

I firmly believe, as someone who has been involved in demonstrating the feasibility of pull based identity architectures for delivering the right information to the right person at the moment of need using current commercial technologies and standards, that we have reached a point in time where the combination of the maturity of approaches and technologies such as the Federal ICAM Backend Attribute Exchange or the Identity Meta-system technologies and the willingness of the Government to engage with the public in the area of identity, that it is time to have a discussion about this topic.

The questions are definitely NOT technical in nature but are more around need and interest, feasibility and value with a heavy infusion of privacy. Some initial questions to start the conversation rolling would be:

• What are a core set of attributes that can serve as a starting point for discussion?
• Who would find value in utilizing them? How is it any better than what they have in place right now?
• What are the privacy implications of specific attributes? How can they be mitigated (e.g. Ask if this person is old enough to buy alcohol vs. What is your birthday/age?
• Liability in case of mistakes
• How would the Government recoup some of the costs? We pay for passport renewals, we pay for driver's license renewals; don't expect this to come for free
• Much, much more....

I would be curious to find out if there is any interest in this topic and if so what your reactions are. If there is interest, and given that the next Internet Identity Workshop is for the first time going to be held on the East Coast (Washington DC) on September 9-10 with a focus on "Open Identity for Open Government", and given its un-conference nature, was going to propose this as a topic of discussion.

UPDATE: Ian Glazer, Research Director for Identity and Privacy at Gartner has agreed to tag team with me on this topic at IIW in DC. Ian's research and interests sit at the very important intersection of Identity and Privacy, and I think he will bring that much needed perspective to this conversation.

He also thought that the topic should be more correctly termed "Government's role as an Oracle" rather than as an Attribute Provider, and since I agree, that will more than likely end up being the topic

To see what is meant by an Identity Oracle and what it is NOT, read this and this blog posts by Bob Blakely

The Gartner/Burton Group conference has a very high signal to noise ratio and is one that I was fortunate to present at this year. I spoke in my role as the Technical Lead for DHS Science & Technology Directorate's Identity Management Testbed about how we are taking the Federal ICAM Backend Attribute Exchange Interface and Architecture Specification from Profile to Usage.

The biggest buzz in the Identity Management track, where I spent most of my time, was around the “pull” based architecture that Bob Blakley and the rest of the Burton crew have been writing and speaking about for a while as being the future of Identity Management. The key take-away’s for me on this topic are:

• We are moving to an era where dynamic, contextual, policy driven mechanisms are needed to make real time access control decisions at the moment of need.
• The policy driven nature of the decisions require that the decision making capability be externalized from systems/applications/services and not be embedded within and that policy be treated as a first class citizen.
• The input to these decisions are based on information about the subject, information about the resource, environmental/contextual information, and more, that are often expressed as attributes/claims.
• These attributes/claims can reside in multiple authoritative sources where the authoritative-ness/relevance may be based on the closeness of a relationship that the keeper/data-steward of the source has with the subject.
• The relevant attributes are retrieved (“pulled”) from the variety of sources at the moment when a subject needs to access a system and are not pre-provisioned into the system.
• Standards! Standards! Standards! All of the moving parts here (finding/correlating attributes, movement of attributes across organizational boundaries, decision control mechanisms etc.) needs to be using standards based interfaces and technologies.

Potential implementation technologies proposed include virtual directories as mechanisms that can consolidate and correlate across multiple sources of attributes, standards such as LDAP(S), SAML and SPML as the plumbing standards, and External Authorization Mangers (“XACMLoids”) as decision engines.

What was interesting and relevant to me is the the US Federal Government via the ICAM effort as well as the Homeland Security, Defense and other communities have embraced this viewpoint for a while and are putting into place both the infrastructure to support it at scale, and have working implementations in use.

In particular my presentation was about how we are working an information sharing effort between two organizations who need to collaborate and share information in the event of a natural or man-made disaster where there is no way we could pre-provision users since we won’t know who those users are until they try to access systems. Our end-to-end implementation architecture really reflects pretty much everything noted in the Burton vision of the future. Relevant bits from the abstract:

The Backend Attribute Exchange (BAE) Interface and Architecture Specifications define capabilities that provide for both the real time exchange of user attributes across federated domains using SAML and for the batch exchange of user attributes using SPML.

The DHS Science & Technology (S&T) Directorate in partnership with the DOD Defense Manpower Data Center (DMDC), profiled SAML v2.0 as part of a iterative proof of concept implementation. The lessons learned and the profiles were submitted to the Federal CIO Council’s Identity, Credentialing and Access Management (ICAM) Sub-Committee and are now part of the Federal Government's ICAM Roadmap as the standardized mechanism for Attribute Exchange across Government Agencies […]

This presentation will provide an overview of the BAE profiling effort, technical details regarding the choices made, vendor implementations, usage scenarios and discuss extensibility points that make this profile relevant to Commercial as well as Federal, State, Local and Tribal Government entities.

In our flow there is a clear separation of concerns between Authentication and Authorization and in the language of my community, the subject that is attempting to access the Relying Party application is an “Unanticipated User” i.e. a subject that is from outside that organization who has NOT been provisioned in the RP Application.

1. There is a organizational access control policy that is externalized from the application via the Externalized Authorization Manager (EAM) that is dynamic in nature (“Allow access to user if user is from organization X, has attributes Y and Z and the current environment status is Green”).
2. The subject is identified as being from outside the organization, is authenticated and an account is created in the system. The subject has no roles, rights or privileges within the system.
3. The EAM pulls the attributes that are needed from external (to organization) sources to execute the access control policy and based on a permit decision grants access to resources that are allowed by policy.

All of this, BTW, is taking place using existing standards such as SAML and XACML and technologies such as Virtual Directories, XML Security Gateways, Externalized Access Management solutions etc. This works now using existing technology and standards and gets us away from the often proprietary, connector-driven, provisioning-dependent architectures and moves us to something that works very well in a federated world.

To us this is not the future of Identity Management. This is Now!

At a meeting yesterday Judy Spencer, co-chair of the Federal CIO Council ICAMSC, briefed that NIST had recently re-released Special Publication 800-73 [PDF] to account for PIV-I Card Issuance.  These would be Smart Cards that can be issued by Non-Federal Issuer’s and can potentially be trusted by US Government Relying Parties.

The relevant bits are in Section 3.3 of NIST SP 800-73-3 (Quoting below so that I can easily reference them in the future):

3.3    Inclusion of Universally Unique IDentifiers (UUIDs)

As defined in [10], the presence of a Universally Unique IDentifier (UUID) conformant to the specification [11] is required in each identification card issued by Non-Federal Issuers, referred to as  “PIV Interoperable” (PIV-I) or “PIV Compatible” (PIV-C) cards.  The intent of [10] is to enable issuers to issue cards that are technically interoperable with Federal PIV Card readers and applications, and that may be trusted for particular purposes through a decision of the relying Federal Department or Agency.  Because the goal is interoperability of PIV-I and PIV-C with the Federal PIV System, the technical requirements for the inclusion of the UUID document are specified in this document. To include a UUID identifier on a PIV-I, PIV-C, or PIV Card, a credential issuer shall meet the following specifications for all relevant data objects present on an issued identification card.

1. If the card is a PIV-I or PIV-C card, the FASC-N in the CHUID shall have Agency Code equal to 9999, System Code equal to 9999, and Credential Number equal to 999999, indicating that a UUID is the primary credential identifier.  In this case, the FASC-N shall be omitted from the certificates and CMS-signed data objects. If the card is a PIV Card, the FASC-N in the CHUID shall be populated as described in Section 3.1.2, and the FASC-N shall be included in authentication certificates and CMS-signed data objects as required by FIPS 201.
2. The value of the GUID data element of the CHUID data object shall be a 16-byte binary representation of a valid UUID[11]. The UUID should be version 1, 4, or 5, as specified in [11], Section 4.1.3.
3. The same 16-byte binary representation of the UUID value shall be present as the value of an entryUUID attribute, as defined in [12], in any CMS-signed data object that is required to contain a pivFASC-N attribute on a PIV Card, i.e., in the fingerprint template and facial image data objects, if present.
4. The string representation of the same UUID value shall be present in the PIV Authentication Certificate and the Card Authentication Certificate, if present, in the subjectAltName extension encoded as a URI, as specified by [11], Section 3.

The option specified in this section supports the use of UUIDs by Non-Federal Issuers.  It also allows, but does not require, the use of UUIDs as optional data elements on PIV Cards.  PIV Cards must meet all requirements in FIPS 201 whether or not the UUID identifier option is used; in particular, the FASC-N identifier must be present in all PIV data objects as specified by FIPS 201 and its normative references.  PIV Cards that include UUIDs must include the UUIDs in all data objects described in (2) through (4).

At the IDManagement.gov site, you can also find a list of Credential Service Providers, cross-certified with the US Federal Bridge CA at Medium Hardware LOA (i.e. Meets the requirement that FIPS 140 Level 2 validated cryptographic modules are used for cryptographic operations as well as for the protection of trusted public keys), who have the ability to issue PIV-I Credentials.

To be conformant to SPML v2 means that the SPML interface (Provisioning Service Provider / PSP) MUST:

• Support the set of Core operations
• a discovery operation {listTargets} on the provider
• basic operations {add, lookup, modify, delete} that apply to objects on a target
• Supports basic operations for every schema entity that a target supports
• Supports modal mechanisms for asynchronous operations

There are additional “Standard” operations described in the OASIS SPML v2 Specification [Zip]. The clear thing to keep in mind is that each operations adds a data management burden onto the provider, so the choice of whether or not to implement them should be considered very carefully.

From the perspective of deployment topologies, the PSP could be deployed separately from the Target or could very well be integrated tightly with the Target e.g. an SPML compliant web service interface on a target system.

One of the frustrating items for me when enquiring about SPML support in products has been the lack of clarity and visibility around exactly what has been implemented. All too often, vendors seem to have cherry picked a chosen set of operations (whether from the Core or from the Standard list) and used that to claim SPML support. I would be very curious to see if anyone can claim full SPML v2 compliance.

A particular use case for SPML that I am currently working on has to deal with the “batch” movement of attributes from multiple systems to a central repository. The typical flow is as follows:

• Per organizational policy & relationship to user, attributes are assigned in their home organization and/or business unit (Org A / Org B / …)
• Org A must move those users and/or their attributes to a central repository (Repository X) on a regular basis
• Repository X acts as the authoritative source of attributes of users from multiple organizations / business units and can provide those attributes to authenticated and authorized entities in a real-time request/response and in a synch-take-offline-use modes.

Some points to keep in mind are:

• Org A / B / … may have, and all too often do, have their own existing identity and provisioning systems as well as associated governance processes in place.
• The organizations and the repository may or may not be under the same sphere of control and as such cannot mandate the use of the same piece of provisioning software and associated connectors on both ends of the divide.
• The systems where the organizations store the attributes of their users may not necessarily be directory based systems.
• The Repository may or may not be directory based system.
• Identity / Trust / Security are, as you may imagine, rather important in these types of transactions.

To meet these needs, we are currently profiling SPML to support the Core SPML Operations as well as the optional “BATCH” capability.  The “ASYNC” capability is something that we are more than likely going to support as well as it provides a mechanism for the provider to advertise support for asynchronous operations rather than have a request for an asynch operation fail on a requester with an error “status=’failed’” and “error=’unsupportedExecutionMode’”.

Keep in mind that the end result will satisfy more than just the one use case that I noted above. In fact, it satisfies many other use cases that we have that deal with both LACS and PACS scenarios. In addition, the profile will also bring in the pieces that are noted as out of scope in the SPML standard i.e. the Profiling of the Security protocols that are used to assure the integrity, confidentiality and trust of these exchanges. Fortunately, we can leverage some of previous work we have done in this space for that aspect.

Mark Diodati at the Burton Group kicked off this conversation in his blog post "SPML Is On Life Support..." Other folks, notably Nishant Kaushik ("SPML Under the Spotlight Again?"), Ingrid Melve ("Provisioning, will SPML emerge?") and Jeff Bohren ("Whither SPML or wither SPML?") bring additional perspectives to this conversation. There is also some chatter in the Twitter-verse around this topic as well.

As someone who has been involved in both the standards process as well as end user implementation, I have a semi-jaded perspective to offer on what it takes for vendors to implement interfaces that are standards based in their tooling/products. First of all, let it be clearly understood that Standards are beautiful things (and there are many of them) but a Standard without vendor tooling support is nothing more than shelf-ware. So in the case of Standards Based Provisioning, in order to get that tooling support, multiple things need to happen:

• First and foremost, do NOT let a vendor drive your architecture! User organizations need to break out the "vicious cycle" that exists by first realizing that there are choices beyond the proprietary connectors that are being peddled by vendors, and secondly by stepping up and defining provisioning architectures in a manner that prioritizes open interfaces, minimizes custom connectors and promotes diversity of vendor choice.  Map vendor technology into your architecture and not the other way around, because if you start from what a vendor's product gives you, you will always be limited by that vendor's vision, choices and motivations.
• Bring your use cases and pain points to the Standards development process and invest the time and effort (Yes, this is often painful and time consuming!) to incorporate your needs into the base standard itself. I am finding that often the Technical Committees in Standards Organizations are proposed and driven by vendors and not end users. But in cases where there is a good balance between end users and vendors, the Standard reflects the needs of real people (The Security Services/SAML TC at OASIS often comes to mind as a good example).
• Organizations need to incorporate the need for open standards into their product acquisition process. This needs to go beyond "Product X will support SPML" to explicit use cases as to which portions of the standard are important and relevant. Prototype what you need and be prepared to ask tough, detailed questions and ask for conformance tests against a profile of the Standard.
• Be prepared to actively work with vendors who treat you like an intelligent, strategic partner and are willing to invest their time in understanding your business needs and motivations. These are the folks who see the strategic value and business opportunities in supporting open interfaces and standards, realize they can turn and burn quicker than the competition, and compete on how fast they can innovate and on customer satisfaction versus depending on product lock-in.  They are out there, and it is incumbent upon organizations to drive the conversation with those folks.

Moving on, let me reiterate the comments that I made on Mark's blog posting:

"The concern with exposing LDAP/AD across organizational boundaries is real and may not be resolved at the technology level. Applying an existing cross-cutting security infrastructure to a SOAP binding (to SPML) is a proven and understood mechanism which is more acceptable to risk averse organizations.

I would also add two additional points:

1. More support for the XSD portion of SPML vs. DSML in vendor tooling. There are a LOT of authoritative sources of information that are simply NOT directories.
2. There needs to be the the analog of SAML metadata in the SPML world (Or a profile of SAML metadata that can be used with SPML) to bootstrap the discovery of capabilities. The "listTargets" operation is simply not enough."

While I do resonate with the "pull" model interfaces noted by Mark in his posting, I do believe that exposing LDAP(S)/AD Interfaces either directly of via Virtual Directories outside organizational boundaries is a non-starter for many organizations.

At the same time I believe there exists options in the current state of technology to provide a hybrid approach that can incorporate both the pull model as well as provide the application of cross-cutting security infrastructure into the mix. The architecture that we are currently using incorporates a combination of both Virtual/Meta Directory capabilities as well as an XML Security Gateway to provide policy enforcement (security and more) when exposed to the outside.

I will also reiterate that there needs to be more support for the XSD portion of SPML vs. DSML. A lot of the authoritative sources of user information that I am dealing with are simply not found in directory services but in other sources such as relational databases, custom web services and sometimes proprietary formats in addition to LDAP/AD.

I hope to post some the use cases for standards based provisioning as well as the details of some of the profiling that we are doing on SPML to satisfy those use cases in future blog posts. Looking forward to further conversations around this topic.

I had a great time at Burton Group's Catalyst Conference this year.  Spent my time between the Identity Management, SOA and Cloud sessions. Also had an opportunity to attend the Cloud Security & Identity SIG session as well.

As the fast-thinking, slow talking, and always insightful Chris Haddad notes on the Burton APS Blog (Chris... enjoyed the lunch and the conversation) "Existing Cloud Computing's momentum is predominantly focused on hardware optimization (IaaS) or delivery of entire applications (SaaS)".

But the message that I often hear from Cloud vendors is:

• We want to be an extension of your Enterprise
• We have deep expertise in certain competencies that are not core to your business, and as such you should let us integrate what we bring to the table into your Enterprise

... and variations on this theme.

But in order to do this, an Enterprise needs to have a deep understanding of its own core competencies, have clearly articulated it's capabilities into distinct offerings, and gone through some sort of a rationalization process for its existing application portfolio.. In effect, have done a very good job of Service Orient-ing themselves!

But we are also hearing at the same time that SOA has lost its bright and shiny appeal and that most SOA efforts, with rare exceptions, have not been successful. For the record, success in SOA to me is not about building out a web services infrastructure, but about getting true value and clear and measurable ROI out of the effort.

So to me, it would appear that without an organization getting Service Orientation right, any serious attempt they make on the cloud computing end will end up as nothing more than an attempt at building a castle on quicksand.

The other point that I noted was that while there were discussions around Identity and Security of Cloud offerings (they still need to mature a whole lot more, but the discussion was still there), there was little to no discussion around visibility and manageability of cloud offerings.  A point that I brought up in questions and in conversations on this topic was that while people's appetite for risk vary, one of the ways to evaluate and potentially mitigate risk was to provide more real time visibility into cloud offerings.  If a cloud vendor's offerings are to be tightly integrated into an Enterprise, and I now have a clear dependency on them, I would very much want to have a clear awareness of how the cloud offerings were behaving.

From a technical perspective, what I was proposing was something very similar in concept to the monitoring (and not management) piece of what WS-Management & WSDM brought to the table on the WS-* front. In effect, a standardized interface that all cloud vendors agree to implement that provides health and monitoring visibility to the organizations that utilize their services. In short, I do not want to get an after-the-fact report on your status sent to me by e-mail or pulled up on a web site, I want the real time visibility into your services that my NOC can monitor. There was a response from some vendors that they have this interface internally for their own monitoring. My response back to them is to expose it to your customers, and work within the cloud community to standardize it such that the same interface exits as I move from vendor to vendor.

As part of the BAE profiling and reference implementation, we have a full test & validation suite.  Our desire has always been to make the barrier to entry for anyone using the test suites to be the minimum it needs to be. As such we focused on creating our test suites using open source tooling so that we could provide a test suite project that an implementer could import into their open source testing tool, point it at their BAE implementation, run it, and get immediate feedback on whether or not their implementation was conformant to the profile.

To that end, we have been using the popular and free soapUI testing tool. Unfortunately, we are running into some limitations in the tool support for SAML 2.0. It would appear that the current soapUI implementation is using the OpenSAML 1.1 implementation and not the current OpenSAML 2.0 which supports SAML v2. In particular, this means that the following functionality that relates to the testing of SAML AttributeRequest/Response are not supported:

• Ability to digitally sign and validate attribute requests and responses using the enveloped signature method
• Ability to utilize the <saml:EncryptedID> as a means of carrying the encrypted name identifier
• Ability to decrypt the <saml:EncryptedAssertion> element sent by the Attribute Authority which contains the encrypted contents of an assertion

This has required us to go thru some gyrations in how we are implementing the test suites, which is making the user experience not as smooth as we would like.

Ideally we would love to continue using soapUI going forward, but we are also on the lookout for other open source tooling that we could utilize for our testing. Suggestions and recommendations from folks who have experienced this issue and have found a resolution would be very much appreciated.

FIPS 201 defines a US Government-wide interoperable identification credential for controlling physical access to federal facilities and logical access to federal information systems.  The FIPS 201 credential, known as the Personal Identity Verification (PIV) Card, supports PIV Cardholder authentication using information securely stored on the PIV Card. Some PIV Cardholder information is available on-card through PIV Card external physical topology (i.e., card surface) and PIV Card internal data storage (e.g.  Magnetic stripe, integrated circuit chip). 

Other PIV Cardholder information is available off-card. Examples of off-card information, say in the First Responder & Emergency Response domain, could be certifications that could be presented by a Doctor or EMT that could verify their claims and allow physical and/or logical access to resources.

Accordingly, the federal government requires a standard mechanism for Relying Parties to obtain PIV Cardholder information (User Attributes), which are available off-card, directly from the authoritative source (Attribute Authority). The authoritative source is the PIV Card Issuing Agency, which is the agency that issued the PIV Card to the PIV Cardholder.  The exchange of these User Attributes between backend systems is known as “Backend Attribute Exchange” (BAE). The architectural vision for the BAE can be found at IDManagement.gov (Direct link to "Backend Attribute Exchange Architecture and Interface Specification" - PDF).

I, and members of my team, have been part of a joint DHS and DOD team that have been working on a proof of concept implementation of the BAE in order to validate the approach, gain valuable implementation experience, and to provide feedback to the relevant governance organizations within the US Federal Government. The results of our work are three-fold:

1. A SAML2 Profile of the BAE, with both normative and informative sections, that provide concrete implementation guidance, lessons learned as well as recommendations for folks seeking to support this profile
2. Reference implementations stood up within the T&E environments of both DHS and DOD for interoperability testing
3. Test suites that can be used by implementers to verify compliance with the profile

I am happy to report that the profile is currently at v1.0 (DRAFT) status, under external review, and that we are scheduled to give a briefing on the work to a sub-committee of the Federal CIO Council later this month. In addition, we have our reference implementations up and running and are putting the finishing touches on the Test Suites.

As someone who has and is participating in industry standards efforts, I am fully aware that one of the critical items for a standard to become successful is for incorporation of the standard into vendor tooling. Some of the choices that we made, beyond satisfying the needed functionality, was to make sure that it was as easy as possible to build in profile support by:

• Not reinventing the wheel; Leverage the conventions and standards established by some of the fine work that has been done to date by the OASIS Security Services (SAML) TC on Attribute Query Profiles
• Keep the delta's as small as possible between the BAE Profile and existing profiles such as the X.509 Attribute Sharing Profile (XASP)
• Provide LOTS of informative guidance
• Striking a balance between making sure that the profile was generic enough to be widely used and deployable, but provided enough information in the message flow for implementers to get full value.

The last item was something that we found to be critical and sometimes contentious to balance. But, we would not be where we are right now, had we not been informed by our actual proof-of-concept implementations. A pure paper effort would have left too many holes to patch.

We have also made an active effort to reach out to vendors, especially in the federation, entitlement management and XML security arenas, and have been gratified by their response in committing to support this profile in their tooling (In some cases, folks already have beta support baked in!). We are fully expecting to highlight and point out those folks during our out-brief later this month. If you are a vendor, want to find out what it takes to support this profile, and are interested in receiving a copy of the v1.0 DRAFT, please feel free to ping me at anil dot john at jhuapl dot edu.

This has been a pretty extensive, exciting and detailed effort and we are very grateful for the senior level support from both Organizations for this effort.  Beyond that, it has been a blast working with some very smart people from both DHS and DOD to make this real.

Digital ID World 2008 is the first IdM conference that I've gone to as part of a team, and given the variety of breakout sessions we decided early on to use the divide and conquer approach based on our areas of interest and expertise.

The following are some highlights on some (not all) of the sessions that I attended and found to be interesting. As with a lot of conferences, there were some sessions that were pretty much disguised vendor pitches which I am not even going to bother with a mention.

Keynote - Identity Assurance: A Backbone For The Identity Marketplace
by Peter Alterman - GSA, Andrew Nash - PayPal, Frank Villavicencio - Citigroup

In some ways this was rehash of the panel on the same topic that was moderated by Mark Diodati at Burton Catalyst but with the addition of Peter Alterman of the GSA, who tends to add a certain amount of ...ah... flair to the conversation

The intent of the Liberty Identity Assurance Framework (IAF) is to develop a framework that leverages the existing work that has been done by EAP, tScheme, US e-Auth etc. to generate an identity assurance standard that is technology agnostic but provides a consistent way of of defining identity credential policy and the process and policy rule set etc.  The IAF consists of four parts (1) Assurance Levels (2) Assessment Criteria (3) Accreditation and Certification Model and (4) Business Rules. You can find out more about it on the IAF Section of the Liberty Alliance Web Site.

What interested me about the entire conversation was the leveraging of OMB M-04-04 and NIST 800-63 to define the assurance criteria but the drive to make a "Liberty Alliance IAF Assurance Token" (if you will) that will be certified to mean the same thing across federations. Mr. Alterman also noted, and I hope that I interpreted this correctly, that the intent from the GSA side would be to not re-invent the wheel but to adopt this IAF framework going forward. He spoke of current inter-federation work he is involved in between NIH and the InCommon Federation that is leveraging this.

During the Q&A session, I brought up the fact that this work is directly focused on AuthN but in general, access to resources is granted based on a variety of factors, only one of which is the strength and assurance of the authentication token. The response is that the Liberty work is deliberately focusing on the AuthN and considers AuthZ to be out-of-scope for their work.

Keynote Presentation: State Of The Industry
by Jamie Lewis - Burton Group

Enterprise IdM is the set of business processes, and a supporting infrastructure, that provides identity-based access control to systems and resources in accordance with established policies.

• Business trends are driving integration across processes and folks are being asked to do more with less.
• SaaS is gaining momentum
Many failures in IdM projects caused by a lack of doing homework and a belief in the silver bullet product etc.

• People manage risk, not products.
• IdM is a means and not an end; It is about enabling capabilities and not an end in itself.
• The Identity Big Bang is around new ways of working, collaborating and communicating
• Make every project an installment on the Architecture and scope the goals to around 3 years.
• Always think about data linking and cleansing

That was the first half of the keynote, but the second half was something I found to be very fascinating and is based on work that Burton has been proposing around the idea of a "Relationship Layer for the Web"

• AuthN and AuthZ are necessary but not sufficient
• Centrism of any kind does NOT work
• Lessons from social science on trust, reciprocity, reputation etc.
• The future of identity is relationships
• Difference between close and distant relationships; Able to make many observations in a close relationship, so able to get good identity information. Not so for distant relationships
• A good relationship provides value to all parties. And it is not just about rights but also obligations
• Values like privacy etc. require awareness of relationship context
• Systems fail if they are not "relationship-aware"
• Difference between Custodial, Contextual and Transactional identities.
  -- Custodial Identity is directly maintained by an org and a person has a direct relationship with the org.
  -- Contextual identity is something you get from another party but there are rules associated with how that identity can be used.
  -- Transactional identity is just the limited amount of info that an RP (?) gets to complete a transaction e.g. Ability to buy alcohol requires a person to be over 18 (?) but in a transactional relationship, you would simply ask the question of "Is this person old enough to buy alcohol?" and the answer would come back as "Yes/No". Compare this to a question of "What is this person's age or birthday?" which releases a lot more info.
• The last type of identity in effect requires the existence of what Burton Calls an "Identity Oracle" (See Bob Blakley's blog entries) that has a primary and trusted relationship with a user as well as with relying party and can stand behind (from a legal and liability perspective) the transactional identity statements that it makes.

I found this entire topic absolutely fascinating as this is so very relevant to a lot of the work that I do around information sharing across organizations that may or may not trust each other for a variety of (sometimes very valid) reasons. Will be actively tracking this area on an ongoing basis.

The Plot To Kill Identity
by Pamela Dingle - Nulli Secundus

I really enjoyed this session by Pamela on the disconnect that currently exists between the needs of the users, what is being asked of the application vendors and the lack of a common vocabulary to express our needs such that there is a change in the same old way of doing business.

• Need for an effort to be consistent all the way at the RFP/RFI time
• Need a common vocabulary when requesting capability from vendors
• Start with:  Provide and Rely support i.e. the ability to choose whether or not a product relies on external identity services or provides its own.
• Pamela also had a great starting set of RFI type questions one can use.. I am hoping that she will post them on her blog.

One of the questions I brought up during the Q&A session was that if I bought in to the Kool-Aid of what she discussed during the presentation (and I do), what would it take to scale the conversation to a larger audience? Bob Blakley, who was also in the audience, chimed in and noted that if Pamela wrote up a white-paper on the topic, he would help her get it published and widely distributed as well.

I would also be very interested in expanding the scope of the sample RFI questions to be grouped by product/project category (and released under an open licence; Creative Commons?) so that folks like me can use them in our RFP/RFIs as well.

There were more sessions that I attended that were interesting such as the Concordia Workshop on "Bootstrapping Identity Protocols: A Look At Integrating OpenID, ID-WSF, WS-Trust And SAML", "Using An Identity Capable Platform To Enhance Cardspace Interactions" and more..

All in all, beyond the sessions themselves, the hall-way conversations and the connections made to be as valuable (or even more so) than just the sessions themselves. I know that I found and made connections with multiple folks who work in my community and am very much looking forward to future collaborations with them and others.

For those of you in the Baltimore/Washington Area, this may be of interest.

Jeff Barr, the Web Services Evangelist for Amazon Web Services, is someone I know and invited out to Johns Hopkins University - Applied Physics Laboratory (JHU/APL) to give a presentation on Amazon's experience in building out and managing their infrastructure. He was gracious enough to accept and will be giving the presentation as part of the APL Colloquium.  Here are the particulars:

Building a 'Web-Scale Computing' Architecture
Wednesday June 6, 2007, 2:00 - 3:00 PM
Parsons Auditorium, JHU/APL

Jeff Barr will provide the blueprint for 'Web-Scale Computing' - enabling businesses to use Amazon Web Services to build an elastic architecture that can quickly respond to demand. Jeff’s presentation will focus on Amazon Simple Storage Service (Amazon S3), Amazon’s Simple Queue Service, and Amazon Elastic Compute Cloud (Amazon EC2) and will include real-world examples of how these services are being used singly and in combination.

Amazon.com spent 12 years and over $1 billion developing a world-class technology and content platform that powers Amazon web sites for millions of customers every day. Today, Amazon Web Services exposes this technology, through 10 open APIS, allowing developers to build applications leveraging the same robust, scalable, and reliable technology that powers Amazon's business.

The APL Colloquium began in 1947. Held weekly, it is one of the longest standing technical and scientific lecture series in the Washington/Baltimore area. The goal of the Colloquium has been to bring to the Laboratory scientific scholars, technical innovators, industry leaders, government sponsors, and policy makers to inform, educate, and enlighten Laboratory staff on what is currently exciting, relevant, and of value to the work of APL.

You are more than welcome to attend as the Colloquia are open to the public. Visitor Guide/Directions can be found on the APL Colloquium web site. And if you found out about this event from this blog entry, please don't forget to stop by and say hello

"The hard problems in distributed computing are not the problems of how to get things on and off the wire. The hard problems in distributed computing concern dealing with partial failure and the lack of a central resource manager. The hard problems in distributed computing concern insuring adequate performance and dealing with problems of concurrency. The hard problems have to do with differences in memory access paradigms between local and distributed entities. People attempting to write distributed applications quickly discover that they are spending all of their efforts in these areas and not on the communications protocol programming interface." 
- A Note on Distributed Computing by Samuel C. Kendall, Jim Waldo, Ann Wollrath and Geoff Wyant

A very good read, and still relevant after 13 years! Thanks for the pointer, Steve.

Be the Software!

J.D. has an entry on how, when working on some type of a R&D project, you go about shortening and getting more bang for the buck with testing user experience models. Key advice is:

... experimented with two techniques:

1. Build modular slideware for visual walkthroughs of task-based features.
2. Be the software.

This radically improved customer verification of the user experience and kept our dev team building out the right experience.

Mocking up in slides is nothing new.  The trick was making it efficient and effective:

1. We prioritized scenarios that were the most risk for user experience.
2. We created modular slide decks.  Each deck focused on exactly one scenario-based task (and scenarios were outcome based).  Modular slide decks are easier to build, review and update.  Our average deck was around six slides.
3. Each slide in a deck was a single step in the task from the user's perspective.
4. Each slide had a visual mock up of what the user would see
5. To paint some of the bigger stories, we did larger wrapper decks, but only after getting the more fine-grained scenarios right.  Our house was made of stone instead of straw.  In practice, I see a lot of beautiful end-to-end scenarios decks that are too big, too fragile and too make believe.

I've seen a couple of examples of this, but my issue with them was exactly what he called out in (5) i.e. "..beautiful end-to-end scenarios decks that are too big, too fragile and too make believe".  Good advice that is very useful. Check out the full entry.

Performance in a SOA, especially in a SOA implemented using Web Services is very important, but folks all too often do not have a common definition of what performance is. In addition, in a majority of the cases, performance is not treated as something that should be engineered into a solution from the ground up.

One of the first things that I do when folks start this particular conversation is to point them to some work that has been done by J.D. Meier and his team over at Microsoft as part of their Perf & Scale work. In particular I point them over to the following:

• Fundamentals of Engineering for Performance
• Performance Modeling
• Design Guidelines for Application Performance

I find the above work relevant, and highly recommended reading, whether or not you are in the .NET/Microsoft, Java/J2EE, OSS or the Fluffy-Bunny camp.

One of the things I like about the Patterns & Practices Team at Microsoft and especially J.D. Meier is that they/he really takes customer feedback into account. The last time I was at Microsoft, I raised some issues that some of the guidance that they provide was too high-level and that they did not break it up into actionable material.

J.D. and his crew have released a new version of the Guidance Explorer that takes into account this feedback. To paraphrase J.D.  "Guidance Explorer let's you browse the online guidance store (caches locally) and you can create your own views of the guidance (or edit the guidance or create your own using our templates or make your own templates). If you don't like what we did, the source is in codeplex so you can shape it to your own needs."

Here are some links that talk in more detail about it:

• J.D's Beta 2 Release post
• .NET 2.0 Performance Guideline (an example)
• Scott Guthrie's (ASP.NET Big Kahuna) post
• Guidance Explorer Web Edition

Very nice work!

Two books that I am currently reading are “Expert .NET Delivery using NAnt and CruiseControl.NET” from Apress and “Ship It! A practical guide to successful software projects”  from the Pragmatic Programmer books series.

I am enjoying both immensely.  I’ve already used the suggestions and recommendations in “Expert .NET Delivery” to improve and fine tune my NAnt scripts and will be moving on to CruiseControl.NET next.  “Ship It!” is in the style of the other Pragmatic books and is an easy and focused read.  I finished it in two days and have already gained a wealth of insight that I can apply immediately.  Highly recommended if you want to streamline your software development life!

Ever since I read the Pragmatic Programmer series of books, I have been a fan of automation. So the build process is one that I have tried to automate to the extent possible. The tool of choice for me in this case has been NAnt. At a high level, my build process consist of the following:

• Clean up the existing directory structure
• Prepare the directory structure
• Get the source from my Source Control Provider
• Build the solution
• Run Unit Tests
• and more...

I was fortunate enough to spend the last three days at the Patterns & Practices Summit which was held at the Microsoft Technology Center in Reston, VA. 

In a word, Awesome!

We had a great lineup of speakers such as:

• Jim Newkirk (Father of NUnit) on Test Driven Development
• Ron Jacobs (Shadowfax Guy) on Patterns for SOA
• Chris Kinsman on Designing for Security and Perf and Scalability
• Fernando Guerrero on Data Access
• Ted Neward on Platform Interoperability and Instrumenting Applications
• Billy Hollis on Smart Client Architecture
• Rocky Lhotka on the Middle Tier
• Tom Hollander on the upcoming Enterprise Library
• Keith Pleas on putting it all together.
• and more...

Beyond the pure technical knowledge that was imparted, it was also a chance to connect in person with people who I had, in some cases, "met" only online. The other great thing was the ability to leverage their knowledge. Chris Kinsman helped me solve a configuration issue that I had been having with Log4Net and Jim Newkirk was a great source of information on some things I am currently looking at regarding Unit Testing, Daily Builds and more.  Tom Hollander as ever was patient in taking some of the "feedback" I have regarding some of the deployment scenarios for the Enterprise Library

Building on the application patterns presented in Enterprise Solution Patterns Using Microsoft .NET, this guide applies patterns to solve integration problems within the enterprise.

The design concepts in this guide include implementations on the Microsoft platform that use BizTalk Server 2004, Host Integration Server 2004, ASP.NET, Visual Studio, Visio 2003 and the .NET Framework.

The scenario is an online bill payment application in the banking industry. To meet the needs of this scenario, the team used a pattern-based approach to build and validate a baseline architecture. Because a well-designed architecture must be traceable to the needs of the business, the guide also includes a set of artifacts that trace from high-level business processes down to code.

Online @
Integration Patterns

Should be available for download as PDF soon.

UPDATE: PDF is now available

patterns & practices Live: Integration Patterns - Level 200
http://go.microsoft.com/fwlink/?LinkId=31149
July 8, 2004, 11:00 AM - 12:30 PM Pacific Time
Gregor Hohpe, Senior Architect, ThoughtWorks, Inc

Today's business applications rarely live in isolation. Users and customers expect instant access to data and functions that may be spread across multiple independent systems. Therefore, these disparate systems have to be integrated to allow a coordinated flow of data and functionality across the enterprise. Despite advances in EAI and Web Services tools, creating robust integration solutions is not without pitfalls. For example, the asynchronous nature of most message-based integration solutions is different from the synchronous world of application development and requires architects and developers to adopt new design, development and testing strategies. This webcast shows how design patterns can help developers build successful integration solutions. The patterns have been harvested from years of actual integration projects using messaging, Web Services and EAI tools.

Per Harry Pierson:

1. Realizing SOA by John deVadoss & Ron Jacobs
2. Data in SOA by Harry Pierson
3. Patterns in the Enterprise by Gregor Hohpe
4. Improving Application Perf & Scale by Chris Kinsman
5. Building Apps with P&P App Blocks by Wojtek Kozaczynsk

 

Per David Hill:

The Smart Client Architecture Guide is now live on MSDN

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scag.asp

The performance chapter is being completed as we speak and should be posted in a week or so. We decided to put the rest of the guide out there since it has generated a lot of interest. Feedback welcome!

 

Implement Presentation Workflow with the User Interface Process Application Block – Level 400
http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032252968&Culture=en-US
June 15, 2004, 1:00PM-2:30PM Pacific Time
Brian Noyes, Principal Software Architect, IDesign, Inc

The User Interface Process (UIP) application block provides a rich framework for developing stateful, process-oriented user interfaces, either for Web or windows applications. It allows you to decouple the views of your application using and implementation of the Model-View-Controller pattern provided by the application block. Ideal for applications such as shopping carts, registration, questionnaires, online quizzes, and other single flow or multi-path information gathering applications, the UIP is a complex framework that is very easy to use. This webcast will step through the architecture and capabilities of the UIP application block and demonstrate when and how to employ it for both web and windows applications.

patterns & practices Live: Testing Blocks - Level 200
http://go.microsoft.com/fwlink/?linkid=29308
June 17, 2004, 11:00 AM - 12:30 PM Pacific Time
Larry Brader, Test Lead, Microsoft Corporation

Blocks have been gaining momentum as their values to developers are realized, but in reality development is only half the equation to shipping a product. The other side is that of Test. In this Webcast we will drill down and examine how to test blocks.

[Editor's note:  Looks like someone is taking a shortcut in the description here.. I assume that the webcast is on how the Application Blocks are tested. Sandy recently blogged [1] about the new guidance that the PAG folks are putting together on this and the related GotDotNet workspace..]

patterns & practices Live: Test Driven Development – Level 200
Ah, the on demand version of this past webcast by Jim Newkirk is now available! [2]

[1] http://blogs.msdn.com/sandyk/archive/2004/06/11/153581.aspx
[2] http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032254189&Culture=en-US

patterns & practices Live: Enterprise Software Architects - Level 200
http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032252958&Culture=en-US
June 10, 2004, 11:00 AM - 12:30 PM Pacific Time
Craig Utley, Partner, Enterprise Software Architects

This webcast will focus on the patterns work going on at Microsoft designed to help developers reap the benefits of pattern-based development. It will give you a sneak peak at some third-party training resources that will help your development teams adopt these proven techniques in your development organization.

Ah.. It is finally up! New site features include:

• Redesign of site navigation allowing you to locate patterns & practices titles by viewpoint, guidance type, or audience, and the ability to locate a title in the all releases list alphabetically. 
• Ability to search exclusively within the patterns & practices site.
• Enhanced community page including a new GotDotNet workspaces page with individual links to each of the patterns & practices workspaces.
• New Case Studies page for highlighting customers that are succeeding with patterns & practices.
• New Events page showing upcoming events where patterns & practices will be participating, upcoming webcasts, as well as all archived webcasts.

Moving to SOA: Practical approaches in Healthcare Level 200
http://go.microsoft.com/fwlink/?linkid=24686
May 18, 2004, 11:00 AM - 12:30 PM Pacific Time
Tim Gruver, Architect Evangelist, Microsoft Corporation

This webcast will focus on practical approaches for migrating to an SOA, while considering the unique challenges of the healthcare industry and government standards.

  
patterns & practices Live: User Interface Process Block Version 2 Level 200
http://go.microsoft.com/fwlink/?linkid=27714
May 20, 2004, 11:00 AM - 12:30 PM Pacific Time
Scott Densmore, SDE, Microsoft Corporation

The User Interface Process (UIP) Application Block, version 2, provides an extensible framework to simplify the process of separating business logic code from the user interface. This webcast will examine using the block to write complex user interface navigation and workflow processes that can be reused in multiple scenarios and extended as your application evolves. UIP Version 2 provides support for both Web Forms and Smart Clients.

This MSDN TV episode is related to the newest release from the patterns & practices team. The topics discussed are memory management, COM Interop and the Dispose pattern.

Check it out @
http://www.microsoft.com/downloads/details.aspx?familyid=9b973ffd-fa90-4ec4-ae05-20f004637e1c

BTW, you can find the online version and a PDF download @
http://msdn.microsoft.com/perf

Integration Patterns from the PAG introduces patterns in the context of the Global Bank integration scenario. This patterns catalog is organized to help you locate the right combination of patterns to apply when solving your integration problem. In addition, the guide introduces a visual model that describes a language of patterns and their relationships.

Improving .NET Application Performance and Scalability from the PAG  is now available as a PDF download.

Go get it NOW @
http://www.microsoft.com/downloads/details.aspx?familyid=8a2e454d-f30e-4e72-b531-75384a0f1c47

UPDATE: Online version can be found @ http://msdn.microsoft.com/perf 

[Now Playing: Laila Laila - Samay]

Architecting and Building Smart Client Solutions: The Future of Application Development Level 200
http://go.microsoft.com/fwlink/?linkid=27649
May 04, 2004, 11:00 AM - 12:30 PM Pacific Time
Tim Huckaby, CEO, InterKnowlolgy

In Spring of 2003, Tim Huckaby was tasked by Microsoft Norway to develop and deliver a keynote-level "Architecting and Building Smart Client Applications" presentation for the Visual Studio .NET 2003 launch in Oslo. In performing the research to put together the content and demos necessary for a great presentation, Tim discovered multiple instances of inconsistent messaging in smart client application development that still exist today. Even today, Microsoft has multiple conflicting definitions of what a smart client application is, and there are still some very distinct and differing "siloed" opinions of smart client applications within the Microsoft Product Groups. Developers won't want to miss this webcast's demonstrations, which will help demystify these inconsistencies and narrow the definition of a smart client application.

Patterns & Practices Live: .Net Enterprise Solution Patterns Level 200
http://go.microsoft.com/fwlink/?linkid=27657
May 06, 2004, 11:00 AM - 12:30 PM Pacific Time
Robert C. Martin, President, Object Mentor Inc

This webcast presents an overview of the .Net Enterprise Solution Patterns. The concept of patterns will be introduced, and a selected group of patterns will be discussed in depth.

Issue 3 is out @
http://msdn.microsoft.com/architecture/community/newsletter/default.aspx

"... this newsletter will keep you informed of all that's new on the MSDN Architecture Center as well as upcoming events. We'll continue to bring you features and profiles from Microsoft architecture community, plus a new feature added this issue called "Contemplating Architecture." This feature offers opinions and perspectives from Microsoft architects and members of the Microsoft Architecture Advisory board."

Patterns & Practices Guide on "Improving .NET Application Performance and Scalability" is now LIVE!

This guide provides end-to-end guidance for managing performance and scalability throughout your application life cycle to reduce risk and lower total cost of ownership. It provides a framework that organizes performance into a handful of prioritized categories where your choices heavily impact performance and scalability success. The logical units of the framework help integrate performance throughout your application life cycle. Information is segmented by roles, including architects, developers, testers, and administrators, to make it more relevant and actionable. This guide provides processes and actionable steps for modeling performance, measuring, testing, and tuning your applications. Expert guidance is also provided for improving the performance of managed code, ASP.NET, Enterprise Services, Web services, Remoting, ADO.NET, XML, and SQL Server.

Check it out @
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scalenet.asp

Congrats to J.D. Meier, Srinath Vasireddy, Ashish Babbar, and Alex Mackman as well as all of the Microsoft and external reviewers who contributed to this guide!

Do I even need to mention that this amazing tome is put out by the MS PAG? *

* Promote the PAG week continues ....

[NOTE: For my non-US readers, Tylenol is a very popular medicine that is taken for headache and fever relief in the US]

I am an unabashed fan of the PAG!

For those who do not know the acronym, the PAG is the Platform Architecture Guidance Group at Microsoft. They are the folks who put out the Patterns & Practices series of books as well the .NET Application Blocks among other things. In a sentence, these are the folks who provide you with the tools and information that demonstrate and document the best practices for implementing the current shipping technology.

Best Practices for Current, Shipping Technology. This is an important distinction.

In a lot of ways the Product Teams at Microsoft live a Rev ahead. They are already working on the next generation (and the one after) of the current technology. When speaking with them the focus often is on what is coming and not on what is currently here. While that is very cool and exciting, it does not address the working concerns of the current technology implementers.

Pop open the latest issue of MSDN Magazine or any of the other .NET trade rags. What do you find these days? Coverage of Visual Studio .NET 2005! Generics in C# 2.0! The magic and the wonder that is Longhorn! Yet these technologies are at best more than a year out. Are you deploying PRODUCTION apps on this technology? Is any Enterprise (other than ones that Microsoft directly supports via its Early Adopter Programs) implementing this technology NOW? The answer is NO! The pain points and the headaches that Enterprises are experiencing are with the current shipping 1.0 or 1.1 .NET Technologies… Heck, many folks are only now thinking of moving to .NET (More on this later..). They have little to no interest in alpha/beta technologies. They have issues that need to be addressed now.

This is where the PAG comes in. They produce the prescription that solves the headaches that Enterprises have RIGHT NOW! They produce the best practices and architecture guidelines that showcase Microsoft technology as being seriously Enterprise ready. Here is a sampling:

• Application Architecture for .NET
• Building Secure ASP.NET Applications
• Enterprise Solution Patterns for .NET
• Improving Web Application Security
• Microsoft Exchange 2000 Server Operations Guide
• .NET Application Blocks
• Microsoft SQL Server 2000 High Availability Series
• Shadowfax SOA Reference Application
• and more…. @ http://www.microsoft.com/resources/practices/

I personally don't think that they get the credit or visibility they truly deserve. The reason of course is that they are not out in front talking about and playing with cool tools and sexy technologies. They are the people who provide the basic blocking and tackling that allows the Quarterback to be a shining star. They do what they do so OTHERS can get the work done. And in that goal, they are immensely successful.

I've been meaning to write about this for some time, but this came up front and center for me very recently. I am currently in the midst of an Architecture consulting gig with a firm that is moving to .NET. I've done this sort of thing before (first time about 2 years ago), when I was the Architect/Technical Lead tasked with implementing .NET for the Fortune 500 Enterprise I was then working at. At that time, a lot of the practices that were implemented were a direct result of my personal knowledge of .NET from working with it from the early beta phases and knowing the right people to ping at Microsoft to get advice on particular issues that I needed help with. What is different now is the breath and depth of material I can tap into from the PAG that make mine and my client's life so much easier. I don't think a day has gone by when we have not reviewed some best practice or implemented something that came out of the PAG. The resources the PAG has provided has allowed my client to have the comfort factor that we are doing the right things with .NET Technologies.

So Kudos and Thank You to Sandy, Shaun, JD, Tom, Ron, Ed, David and the many more folks at PAG.

If you take away one thing from this entry, it is that when you run into issues or need guidance on current technologies, do go over to the PAG site @ http://www.microsoft.com/resources/practices/ and browse over their offerings. I would not be surprised if you come away with answers or pointers to answers that heal YOUR pain!

[Changed my mind just this once, about Longhorn stuff. Only because it is from my favorite people @ the PAG]

The Developer Guide to Migration and Interoperability in "Longhorn" is a patterns & practices "Emerging Practice" that provides developers with a roadmap for how to start preparing for Longhorn today. It addresses these issues from two main vantage points. First, from an architectural perspective, it looks at considerations and decisions that are optimal for establishing an infrastructure for Longhorn applications. Second, from a development perspective, it delves into low-level coding recommendations for when and how to interoperate and/or migrate existing code. These recommendations include new best practices around managed/unmanaged code integration that are relevant to all mixed mode development. The recommendations also include deep discussion on the presentation layer, in terms of migration and interoperability, of Win32, ActiveX, and Windows Forms with the new presentation capabilities in Longhorn. 

Check it out @
http://msdn.microsoft.com/longhorn/understanding/books/migrationguide/

Architecting and Building Smart Client Solutions: The Future of Application Development - Level 200 [1]
April 22, 2004, 9:00 AM - 10:30 AM Pacific Time
Tim Huckaby, CEO, InterKnowlolgy

In Spring of 2003, Tim Huckaby was tasked by Microsoft® Norway to develop and deliver a keynote level "Architecting and Building Smart Client Applications" presentation for the Microsoft® Visual Studio® .NET 2003 launch in Oslo. In performing the research to put together the content and demos necessary for a great presentation, Tim discovered multiple instances of inconsistent messaging in smart client application development that still exists today. Even today, Microsoft has multiple conflicting definitions of what a smart client application is and there are still some very distinct and differing "siloed" opinions of smart client applications within the Microsoft Product Groups. Developers won't want to miss this webcasts demonstrations that will help demystify these inconsistencies and narrow the definition of what a smart client application is.

  
Patterns & Practices Live: P&P Update - Level 200 [2]
April 22, 2004, 11:00 AM - 12:30 PM Pacific Time
Sandy Khaund, Group Product Manager, Microsoft Corporation

This webcast will be a patterns & practices Spring 2004 Update. This is a follow-up to the October 2003 webcast about patterns & practices, the library of guidance and code to help build sound solutions for the .NET Framework. In this webcast, we will provide an overview of the upcoming deliverables provided by patterns & practices (Shadowfax, Performance & Scalability, Integration Patterns) and give you a preview of other activities that the team will be pursuing in the months ahead.

[1] http://go.microsoft.com/fwlink/?linkid=25881
[2] http://go.microsoft.com/fwlink/?linkid=25880

I am in the process of architecting a thick client distributed application that also has application integration business requirements. Looking through the various Distributed Systems Patterns in the Patterns & Practices "Enterprise Solution Patterns using Microsoft .NET v 2.0", the Data Transfer Object (DTO) Pattern maps very well into the path that we have chosen (WinForms <--> WS <--> Biz/Data).

While I was initially looking at implementing the DTO using a typed DataSet, I am concerned with the potential performance hit (Instantiation/ Filling/ Serialization/ Deserialization) when using a DataSet. Also, in this particular use case, the interaction is with a single table. The recommended alternative for better performance in this case is to use a DataReader with strongly typed objects. The implementation of which is supposedly documented in "Implementing DTO in .NET with Serialized Objects". 

But while this is referenced multiple times as a Related Pattern, I can't seem to find it in the book. Is this missing or is it in some other corner of the book that I have not perused as of yet?

[Now Playing: Jaage Jaage - Mere Yaar Ki Shaadi Hai]

Keith Pleas just blogged that the Microsoft Architecture Center has an RSS feed. Subscribed!  You can find it @ http://msdn.microsoft.com/architecture/rss.xml

BTW, Keith is one of the main people on the GAPP (Guidance About Patterns & Practices) Team, a team of third-party subject matter experts that work closely with the PAG (Prescriptive Architecture Guidance) team to create material that promotes and enhances PAG’s Patterns & Practices titles. He is also the guy putting together the Patterns & Practices Summit.

You can find out more about the GAPP in the following On Demand Webcast @
http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032249518&Culture=en-US

More info on the Patterns & Practices Summit @
http://www.pnpsummit.com/

Keith's blog can be found @ http://weblogs.asp.net/kpleas/

Design and Architecture for .NET Applications - Level 300
http://go.microsoft.com/fwlink/?linkid=25743
April 13, 2004, 11:00 AM - 12:30 PM Pacific Time
Rockford Lhotka, Technology Evangelist and CEO, Magenic Technologies

There are many ways to architect a .NET application. Based on Magenic's architecture experience with .NET at numerous clients, learn which ways work best for Web and Microsoft Windows development. Discover when to use object-oriented designs, and when to use data-centric designs. Find out when to use and not to use Enterprise Services, Remoting, Web services, and other key .NET technologies.

Patterns & Practices Live: Powered by LogicLibrary Logidex - Level 200
http://go.microsoft.com/fwlink/?linkid=25875
April 15, 2004, 11:00 AM - 12:30 PM Pacific Time
Brent Carlson, Vice President of Technology and Co-founder, LogicLibrary

Patterns offer proven solutions to recurring application architecture, design, and implementation problems within a particular context. The Microsoft(r) Platform Architectural Guidance (PAG) Group has developed a number of patterns and best practices for use by architects and developers as they design and build enterprise solutions. The MSDN Logidex .NET Library, powered by LogicLibrary Logidex, provides fast, easy access to the PAG patterns and practices on MSDN. This webcast will use the .NET PetShop reference application to introduce participants to the text and model-based search capabilities of Logidex and to the content of the Logidex .NET Library, showing how the various components of this application are related to PAG-provided patterns and application blocks and to core .NET Framework capabilities.

The Microsoft Patterns & Practices Group has released Version 2.0 of the User Interface Process Application Block.

Overview

The User Interface Process Block V2 or UIP V2 is the next version of one of the most popular application blocks. This block is a reusable code component that builds on the capabilities of the Microsoft .NET Framework to help you separate your business logic code from the user interface. The UIP Application Block is based on the model-view-controller (MVC) pattern. You can use the block to write complex user interface navigation and workflow processes that can be reused in multiple scenarios and extended as your application evolves.

The following features are in the first version of UIP and continue to be part of UIP version 2.

• Web session resume
• Web session transfer
• Reuse of code between application types
• Development of discrete tasks
• Storage of state in state persistence providers
  

The following features are new to UIP version 2:

• Expanded navigation management
• Additional state persistence providers
• Layout managers
• Enable back-button support
• Usability enhancements
• Support for Smart Client Applications, including state persistence using isolated storage
• New views supported: hosted controls, wizards, and floating windows
• A number of fixes and enhancements to V1.

Per Srinath, the Microsoft Patterns & Practices Group has released three chapters (pre-alpha) of the Smart Client Architecture Guide [1]

The chapters are:

1. Introduction
2. Offline
3. Multithreading

The Webcast will be held on April 8, 2004, from 11:00 AM to 12:30 PM Pacific Time (GMT-8, US & Canada). It will be led by Jim Newkirk, Development Lead at Microsoft Corporation and co-author of the book Test Driven Development in .NET.
[testdriven.com]

Here is the official blurb:

In Kent Beck's book titled "Test-Driven Development, By Example" he defines Test-Driven Development (TDD) as driving software development with automated tests. He goes further by stating that TDD is governed by two simple rules: Write new code only if an automated test has failed and eliminate duplication. The implications of these two simple rules can proffer a profound change to the way that software is written. Most of the literature to date has bundled TDD along with Extreme Programming (XP). However, the benefits of using TDD are not limited to XP, and can be realized in any programming methodology. This webcast will provide an introduction into TDD, demonstrating how it works and what benefits it provides when used with Microsoft® .NET. The examples shown will use Visual C#® and NUnit.

This is a Patterns & Practices Group Level 400 Webcast. The link to register can be found @ http://go.microsoft.com/fwlink/?LinkId=25871

Maxim Karpov has a weblog @ http://ipattern.com/simpleblog/ in which he discusses .NET Design Patterns, Best Practices and More. Subscribed!

He also has a recent article in which he implements a wrapper class that uses the Abstract Factory Pattern to implement various Crypto Functions [1]

[1] http://ipattern.com/simpleblog/PermLink.aspx?entryid=19

Sandy Khaund, of the MS PAG, is asking for input into the current and future direction of the .NET Application Blocks on his weblog.  Here is a chance to make your views known [1].

[1] http://blogs.msdn.com/sandyk/archive/2004/03/02/82914.aspx

The Offline Application Block, which is intended to serve as an architectural model for developers who want to add offline capabilities to their smart client applications is now available from the MS PAG [1].

The block demonstrates how to:

• Detect the presence or absence of network connectivity.
• Cache the required data so that the application can continue to function even when the network connection is not available.
• Synchronize the client application state and/or data with the server when the network connection becomes available.

I have added the Offline Block to my complete list of .NET Application Blocks [2]

[1] http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/offline.asp
[2] http://cyberforge.com/weblog/aniltj/articles/217.aspx

The Microsoft Architecture Update is a newsletter for business, applications, infrastructure, and technology architects with essential information on current publications, events, and discussions. It is published every other month via email.

The current issue (February 13, 2004) [1] has the following topics:

• What Makes a Smart Client So Smart?
• Microsoft Architect Advisory Board Holds Inaugural Meeting
• Meet the Architect Advisory Board: Martin Fowler
• Calendar of Events
• TheServerSide.NET Launches
• Smart Client Offline Application Block Set For Mid February
• Community Connection
• The Architect Journal
• Architect Profile: David Hill

Note to Editor:  Proof read! Ex. The link to the online version from the Email version went to a domain called msdnprod. I am sure that works from within MS, but does not from elsewhere   Hopefully these are simple growing pains which are more than offset by the quality content.

Join top experts discussing a wide range of key architectural topics in live, interactive webcasts. Air your questions in the live Q&A sessions.
[MSDN Just Published]

 

I did my first web cast the week before last. A colleague and I, Brenton Webster, who is also a solution architect in the .NET Enterprise Architecture Team, co-presented a session on Smart Client Architecture.

Now, Smart Client Architecture is a big topic and we didn’t have time to cover all architectural issues, but we did cover some of the most frequently asked questions – such as business value, design patterns, deployment and how to go offline. The session is not very technical and was intended more as an overview to the topic but I hope you find it useful…

http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032244110&Culture=en-US
[Microsoft WebBlogs]

DevDays has a Smart Client Track in which the topics will drill down into a lot more technical detail, especially as regards to security.  But high level overviews are a good start.

[Now Playing: O Haseena Zulfon Wali (I) - Dil Vil Pyar Vyar]

I like them as they are extensively tested and reviewed (which hopefully minimizes security issues).

I noted earlier that the PAG had released a new App Block.

Here is a complete list of the App Blocks [1] and where you can download them. I will keep the list up to date as new ones are released.

[1] http://CyberForge.com/weblog/aniltj/articles/217.aspx