MSDN Magazine - June 2008 - (Page 53)

the operation must be either Listen or Send. For example, {URI}#Listen allows the user to start a service endpoint listening on the specified URI, whereas {URI}#Send allows the user to send a message to the specified URI. Custom Token Providers Earlier we mentioned it’s usually odd for a server application to have an interactive login screen like the Windows CardSpace selector appear when the server begins listening. This happens because each endpoint that uses RelayBinding employs an object that implements the ITokenProvider interface. The default implementation for this interface is CardspaceTokenProvider, Figure 8 BizTalk Services Web Site Claim Mapping UI which causes the Windows CardSpace selector to appear when a connection is made to Biz- base class found in the SDK implements both ITokenProvider and Talk Connectivity Services. IEndpointBehavior). In addition to CardspaceTokenProvider, the SDK contains a few more implementations of ITokenProvider. UsernameTokenProvider How to Get Started retrieves a token using a registered username and password from If you’d like to get started with BizTalk Services, first browse to the BizTalk Identity Services. AutomaticRenewalTokenProvider labs.biztalk.net and create an account. You’ll need to ensure that you causes the Windows CardSpace selector to appear, but it will au- have the .NET Framework 3.0 installed, and then you can downtomatically get a new token before the current token expires, en- load and install the BizTalk Services SDK. Once you have an acabling configure-once endpoints. Both of these implementations count in place and the SDK installed on your machine, you should are also endpoint behaviors that can be added to a client or service be able to recreate the samples we’ve shown you in this article. Of endpoint to replace the default CardspaceTokenProvider. course, you’ll need to change the account name used in the URIs Our service can now avoid the interactive login by configuring from “contoso” to your account name. Also, the SDK comes with UsernameTokenProvider on its endpoint before calling Service- some additional samples for your perusal, which may help better Host.Open, as shown here: illustrate some of the concepts we’ve covered. As you get started, ServiceHost sh = new ServiceHost(typeof(SalesService)); if you have additional questions, be sure to check out the FAQ on ServiceEndpoint se = sh.AddServiceEndpoint(typeof(ISalesService), the BizTalk Services site. Good luck!  new RelayBinding(), "sb://connect.biztalk.net/services/contososervices/SalesService"); UsernameToken token = new UsernameTokenProvider("someusername", "somepassword"); se.Behaviors.Add(token); sh.Open(); Jon Flanders is an independent consultant, speaker, and trainer for Pluralsight. So now whenever the service process starts, it will automatically authenticate with BizTalk Identity Services without any human intervention. Alternate implementations of ITokenProvider can also be configured on your RelayBinding endpoint by simply adding the implementation as an endpoint behavior (the TokenProvider He specializes in BizTalk Server, Windows Workflow Foundation, and Windows Communication Foundation. You can reach Jon at masteringbiztalk.com/ blogs/jon. aaron skonnard is a cofounder of Pluralsight, a premier Microsoft .NET training provider. Aaron is the author of numerous books, white papers, and articles as well as Pluralsight’s Applied Windows Communication Foundation, Applied BizTalk Server 2006, and Applied Web Services courses. You can reach him at pluralsight.com/aaron. msdnmagazine.com June 2008 53 http://labs.biztalk.net http://masteringbiztalk.com/blogs/jon http://masteringbiztalk.com/blogs/jon http://pluralsight.com/aaron http://msdnmagazine.com

Table of Contents Feed for the Digital Edition of MSDN Magazine - June 2008

MSDN Magazine - June 2008 Contents Toolbox CLR Inside Out Cutting Edge Patterns In Practice SAAS Concurrency Robotics Form Filler GUI Library Service Station Foundations Windows With C++ Concurrent Affairs Going Places { End Bracket }

MSDN Magazine - June 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.