<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0" 
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:admin="http://webns.net/mvcb/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">

<channel>
<title>herveyw&apos;s blog</title>
<link>http://www.dynamic-cast.com/</link>
<description>Authorization in a Federated World</description>
<dc:language>en-us</dc:language>
<dc:creator>herveyw@mail.dynamic-cast.com</dc:creator>
<dc:date>2005-05-13T22:46:12-08:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=3.15" />
<sy:updatePeriod>daily</sy:updatePeriod>
<sy:updateFrequency>2</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>

<item>
<title>Identity Backgrounders</title>
<link>http://www.dynamic-cast.com/mt-archives/000076.html</link>
<description>A couple of documents worth reading to get some context on what we&apos;re doing in the Identity space: The Identity MetaSystem The Laws of Identity...</description>
<guid isPermaLink="false">76@http://www.dynamic-cast.com/</guid>
<dc:subject>Identity and Access</dc:subject>
<dc:date>2005-05-13T22:46:12-08:00</dc:date>
</item>
<item>
<title>Moving On...Federation Calls...</title>
<link>http://www.dynamic-cast.com/mt-archives/000075.html</link>
<description>I&apos;ve been silent the last few months on WSE topics, the reason is actually simple: at the turn of the year I changed roles (was he pushed or did he jump?) to work on Active Directory Federation Server (ADFS) and InfoCard. ADFS will ship as part of the Windows Server 2003 R2 release and implements the WS-Federation Passive Profile, over time ADFS will evolve to become a full-blown WS-Federation / WS-Trust Security Token Service. InfoCard, a system for managing your identities, will be part of Indigo. Whilst I&apos;m a little sad to have left WSE behind, I&apos;m sure that Mark...</description>
<guid isPermaLink="false">75@http://www.dynamic-cast.com/</guid>
<dc:subject>General</dc:subject>
<dc:date>2005-05-13T09:25:27-08:00</dc:date>
</item>
<item>
<title>SHA-1 Broken?</title>
<link>http://www.dynamic-cast.com/mt-archives/000074.html</link>
<description>Bruce Schneier is reporting that SHA-1 has been broken. Interesting....</description>
<guid isPermaLink="false">74@http://www.dynamic-cast.com/</guid>
<dc:subject>WS-Security</dc:subject>
<dc:date>2005-02-16T08:05:18-08:00</dc:date>
</item>
<item>
<title>UsernameToken Security</title>
<link>http://www.dynamic-cast.com/mt-archives/000073.html</link>
<description>Matt Powell links to an article by Keith Brown on UsernameToken security. Worth reading....</description>
<guid isPermaLink="false">73@http://www.dynamic-cast.com/</guid>
<dc:subject>WSE</dc:subject>
<dc:date>2005-02-07T21:17:57-08:00</dc:date>
</item>
<item>
<title>WSE 2.0 Hands On Lab Updated</title>
<link>http://www.dynamic-cast.com/mt-archives/000072.html</link>
<description>The Hands On Lab materials for WSE have been updated for the WSE 2.0 SP2 release and now include VB.NET code as well as C#. If you&apos;re looking to get started with WSE 2.0, these provide some great grounding material....</description>
<guid isPermaLink="false">72@http://www.dynamic-cast.com/</guid>
<dc:subject>WSE</dc:subject>
<dc:date>2004-12-03T14:31:24-08:00</dc:date>
</item>
<item>
<title>WSE 2.0 SP2 Golden</title>
<link>http://www.dynamic-cast.com/mt-archives/000071.html</link>
<description>Service Pack 2 is final and available on MSDN. There was one additional fix between the Pre-Release and the final build involving policy processing for clients that do not send the WS-Addressing headers. In this case, request policy was being applied correctly but response policy would not be applied. Please report any issues you find on the product to wsefeed....</description>
<guid isPermaLink="false">71@http://www.dynamic-cast.com/</guid>
<dc:subject>WSE</dc:subject>
<dc:date>2004-12-03T10:58:22-08:00</dc:date>
</item>
<item>
<title>WSE 2.0 on .NET FX 2.0 - Update</title>
<link>http://www.dynamic-cast.com/mt-archives/000070.html</link>
<description>.NET Framework 2.0 is still a moving target for the WSE team but things have stabilized a lot recently. We made a few tweaks inside the WSE 2.0 SP2 PreRelease plus got a few bugs fixed in the framework itself. The net result is that we believe that WSE 2.0 SP2 will run correctly on .NET Framework 2.0. Note that this only applies to 32bit mode - there&apos;s no support in WSE2 for 64bit execution....</description>
<guid isPermaLink="false">70@http://www.dynamic-cast.com/</guid>
<dc:subject>WSE</dc:subject>
<dc:date>2004-11-27T10:35:39-08:00</dc:date>
</item>
<item>
<title>Multiple Security Headers</title>
<link>http://www.dynamic-cast.com/mt-archives/000069.html</link>
<description>SoftwareMaker (William T) has a long entry on multiple security headers. Here&apos;s how we thought about the problem for WSE2: In general, you cannot have 2 security headers that target the same node, even if they have different s:Actor values; i.e., one has s:Actor missing and one has s:Actor of next. This is because headers can be re-ordered in messages leading to problems verifying signatures or decrypting elements. This is a simple extension of the highlighted text that is quoted from the WS-Security specification: &quot;Message security information targeted for different recipients MUST appear in different header blocks. This is due...</description>
<guid isPermaLink="false">69@http://www.dynamic-cast.com/</guid>
<dc:subject>WS-Security</dc:subject>
<dc:date>2004-11-27T10:05:41-08:00</dc:date>
</item>
<item>
<title>WSE 2.0 SP2 PreRelease</title>
<link>http://www.dynamic-cast.com/mt-archives/000068.html</link>
<description>A pre-release builds of WSE 2.0 Service Pack 2 is now available. The download links are: WSE 2.0 SP2 PreRelease Full Product WSE 2.0 SP2 PreRelease Runtime Product Here&apos;s the content from the readme file: Core product changes: A new compatibility section is used to select the wire format on the sending side. The mode attribute tells WSE runtime to generate a message which will be compatibable to a particular release of WSE. By default, the mode is WSE2RTM. It can be WSE2RTM, WSE2SP1 WSE2SP2 and so on. On the receiving end, a particular version of WSE runtime will be...</description>
<guid isPermaLink="false">68@http://www.dynamic-cast.com/</guid>
<dc:subject>WSE</dc:subject>
<dc:date>2004-11-22T17:38:18-08:00</dc:date>
</item>
<item>
<title>Keith Moves On</title>
<link>http://www.dynamic-cast.com/mt-archives/000066.html</link>
<description>Words from the man himself (actually, he&apos;s half the man he used to be as you can see here): After many years of work on Web services and WSE, I’ve decided to move on. Starting next week, I’ll be working on the Windows Media Player team. I’ve appreciated working with many of you and can’t describe how great it feels to have so many cool people using this product. I wish you all the best in your future endeavors. I have mixed feelings on this one, Keith and I were the first people on the WSE team back in the...</description>
<guid isPermaLink="false">66@http://www.dynamic-cast.com/</guid>
<dc:subject>General</dc:subject>
<dc:date>2004-09-29T00:10:47-08:00</dc:date>
</item>
<item>
<title>UsernameToken - SendHashed</title>
<link>http://www.dynamic-cast.com/mt-archives/000065.html</link>
<description><![CDATA[Scott Watermasysk posts about UsernameToken hashed passwords and Julia Lerman adds comments in which she says &quot;the database needs to store clear text&quot; although the recommended method is to &quot;store a user's password as a hash, or even better a salted hash&quot; in the database. I've thought about these posts a bit, here are my comments, hopefully they'll be useful for people trying to use these schemes. First, some basics. The word password, when used with the UsernameToken means password or password equivalent. There is absolutely no requirement that the value you use to construct the UsernameToken at the client...]]></description>
<guid isPermaLink="false">65@http://www.dynamic-cast.com/</guid>
<dc:subject>WSE</dc:subject>
<dc:date>2004-09-10T00:39:00-08:00</dc:date>
</item>
<item>
<title>WSE 2.0 on .NET Framework 2.0</title>
<link>http://www.dynamic-cast.com/mt-archives/000063.html</link>
<description>The WSE team recently ran a series of test passes with WSE 2.0 on .NET Framework 2.0 Beta 1 (aka Whidbey or VS 2005). We tried both the shipping version of WSE 2.0 and a recompiled version, but experienced a number of problems with both. We know for sure that the soap.tcp transport is completely broken - incoming connections generally fail with a SocketException during Accept processing. We&apos;ve also run into a number of problems associated with ASMX classes. We&apos;re working with the relevant parties on the Framework team to try to resolve these issues, we believe that most of...</description>
<guid isPermaLink="false">63@http://www.dynamic-cast.com/</guid>
<dc:subject>WSE</dc:subject>
<dc:date>2004-08-24T21:58:25-08:00</dc:date>
</item>
<item>
<title>What&apos;s going on in WSE land?</title>
<link>http://www.dynamic-cast.com/mt-archives/000062.html</link>
<description>The plate is full right now for the WSE team, we have three pieces of work underway concurrently keeping everyone on the team busy (along with all those summer vacations, of course). First up is the C# implementation of the WS-I compliance test tools. I doubt many people know that this is also developed by the WSE team. Right now, the focus is on completing the implementation and testing of various Basic Profile and Basic Security Profile assertions. The BSP assertions right now are limited to examining the message without unravelling the signatures and encryptions; further on down the road...</description>
<guid isPermaLink="false">62@http://www.dynamic-cast.com/</guid>
<dc:subject>WSE</dc:subject>
<dc:date>2004-08-12T23:25:29-08:00</dc:date>
</item>
<item>
<title>WSE 2.0 Service Pack 1 - Update</title>
<link>http://www.dynamic-cast.com/mt-archives/000061.html</link>
<description>Several people have asked how soon this will be released. It should have been early last week but an interoperability problem came to our attention and needed to be investigated prior to release of the service pack. That investigation is now complete and no changes were needed to the service pack; as a result, it should appear within next few days. Now I can go back to my vacation... :-)...</description>
<guid isPermaLink="false">61@http://www.dynamic-cast.com/</guid>
<dc:subject>WSE</dc:subject>
<dc:date>2004-07-25T19:53:38-08:00</dc:date>
</item>
<item>
<title>WSE 2.0 Service Pack 1</title>
<link>http://www.dynamic-cast.com/mt-archives/000060.html</link>
<description><![CDATA[Service Pack 1 will be released very shortly. We've tried to address the major pain points that people found after the product was released. Here's a list of the changes from the readme file: Core product changes: WSE no longer throws an exception due to a SOAP message being signed by a KerberosToken security token in a time zone east of GMT. The value of the maxTokens attribute for the &lt;limits&gt; element specifies the maximum number of security tokens that may be contained within an incoming SOAP message. Previously, only natively supported security tokens counted towards the limit. All members...]]></description>
<guid isPermaLink="false">60@http://www.dynamic-cast.com/</guid>
<dc:subject>WSE</dc:subject>
<dc:date>2004-07-15T17:45:53-08:00</dc:date>
</item>


</channel>
</rss>