If you have developed a claims aware federated application (relying party) using Windows Identity Foundation (WIF), you may have noticed that when you type the URL of your application, you get redirected to the configured STS, get authenticated and all that token dance and when finally everything is working and you the redirect you get back to the relying party application boom!… you get the following error…
ID3206: A SignInResponse message may only redirect within the current web
application: ‘/xxxxx’ is not allowed.
Turns out (after wasting enough time figuring out what happened and searching for answers on the internet if you are a newbie), you missed the trailing slash ‘/’ at the end of the URL to your relying party…
Frustrating isn’t it? There are multiple ways to fix this problem… here is a quick way to solve this…
You can check for the trailing slash ‘/’ and redirect in the Application_BeginRequest method of global.asax as shown below
private void Application_BeginRequest(object sender, EventArgs e)
if (String.Compare(Request.Path, Request.ApplicationPath, StringComparison.InvariantCultureIgnoreCase) == 0 && !(Request.Path.EndsWith(“/”)))
Response.Redirect(Request.Path + “/”);
The BizTalk product group decided to do a major release… instead of BizTalk 2010 R2, announced the release of BizTalk Server 2013 Beta yesterday…
Download here : http://www.microsoft.com/en-us/download/details.aspx?id=35553
BizTalk now supports the latest and greatest in Microsoft technologies including .NET 4.5, Visual Studio 2012, SQL Server 2012 among others…
Other much sought after features include:
- Integration with Cloud Services – BizTalk Server 2013 Beta includes new out-of-the box adapters to send and receive messages from Windows Azure Service Bus.
- RESTful services – BizTalk Server 2013 Beta provides adapters to invoke REST endpoints as well as expose BizTalk Server artifacts as a RESTful service.
- Enhanced SharePoint adapter – Integrating with SharePoint using BizTalk Server 2013 Beta is now as simple as integrating with a file share.
- SFTP adapter – BizTalk Server 2013 Beta enables sending and receiving messages from an SFTP server.
- ESB Toolkit integration – With BizTalk Server 2013 Beta, ESB Toolkit is now fully integrated with BizTalk Server. Also, the ESB Toolkit configuration experience is vastly simplified to enable a quick setup.
- Dependency tracking – The dependencies between artifacts can now be viewed and navigated in Admin console.
- Improvements in dynamic send ports – BizTalk Server 2013 Beta provides the ability to set host handler per adapter, instead of always using the default send handler of the adapters
You know that BAM is used to gather statistics from your BizTalk application. What you probably don’t know is that:
- You can collect BAM data from your non-BizTalk applications such as external .NET components that BizTalk calls into.
- Tracking profile editor (TPE) is not the only way to collect data you can use a set of APIs available in the Microsoft.BizTalk.Bam.EventObservation namespace to read and write directly into the BAMPrimaryImport database.
Check out some of the links here:
Most of you might have come across situations where you have to map a huge number of elements from the source schema to the target schema using the BizTalk Mapper.
There is an easy way to do this depending on your source and target schema structures.
Actually there are two scenarios where you can make use of this: 1. If your source and target schemas have an identical structure, or even if a part of your source schema and target schema have an identical structure.
2. If your source and target schemas have an identical node names, or even if a part of your source schema and target schema have an identical node names.
Here’s how to do it: 1. Bring up your BizTalk mapping editor and load the source and target schemas
To Auto Map by Structure 2. Click on the grid surface of the map and in the properties window and set the “AutoLink By” property to “Structure” (which is actually the default value)
To Auto Map by Node Name 2. Click on the grid surface of the map and in the properties window and set the “AutoLink By” property to “Node Name”
3. Map the nodes by holding down the SHIFT key and drawing a line from the parent node of the source schema to the parent node in the target schema as shown in the figure below:
Note that in our figure above, the node names as well as the structure is the same, so you could set the “AutoLink By” property to either “Structure” or “Node Names” in this case.