In the previous blog post I demonstrated how I can secure my internal BizTalk services application with requirements for Federated Security based on SAML tokens. The goal was to enable my BizTalk service to be a “claims-aware” application. Just like with all other cases of virtualizing BizTalk services through Sentinet, turning the BizTalk service application into a “claim-aware” application did
Search this Site:
Recent Posts
- There was a failure executing the send pipeline: Microsoft.BizTalk.DefaultPipelines.XMLTransmit, Microsoft.BizTalk.DefaultPipelines, …. – This Assembler cannot retrieve a document specification using this type: namespace#rootnode
- BizTalk Server WCF-SQL: Invalid object name while using temporary tables
- Friday Fact: Response Connector Do Not Perform A Schema Validation At Runtime: Workaround!
- BizTalk Server WCF-SQL: The certificate chain was issued by an authority that is not trusted.
- Logic App Transformation Error: InvalidXml. The XML validation failed. Data at the root level is invalid.