Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
SOA Patterns with BizTalk 2013, Second Edition

You're reading from   SOA Patterns with BizTalk 2013, Second Edition Learn how to create and implement SOA strategies on the Microsoft technology stack using BizTalk Server 2013 and Azure Integration platforms

Arrow left icon
Product type Paperback
Published in Jun 2015
Publisher
ISBN-13 9781784396466
Length 508 pages
Edition 1st Edition
Arrow right icon
Toc

Table of Contents (16) Chapters Close

Preface 1. Building BizTalk Server 2013 Applications 2. Windows Communication Foundation Primer FREE CHAPTER 3. Using WCF Services in BizTalk Server 2013 4. REST and JSON Support in BizTalk Server 2013 5. Azure BizTalk Services 6. Azure Service Bus 7. Planning Service-oriented BizTalk Solutions 8. Schema and Endpoint Patterns 9. Asynchronous Communication Patterns 10. Orchestration Patterns 11. Versioning Patterns 12. Frameworks and Tools 13. New SOA Capabilities in BizTalk Server 2013 – Azure Hybrid Patterns 14. What's New and What's Next? Index

Security


The Service Bus Namespace owner account should not be shared or embedded in code. This is a highly privileged account that gives rights to delete and create Azure artifacts and should only be used for administrative tasks.

There are two options available for clients to be authenticated to allow access to the Service Bus:

  • Shared Access Signature (SAS): This provides authentication using a shared key configured on the namespace or on a Service Bus entity (Queues, Topics, and Subscriptions) with specific rights for Listening, Sending, or Managing. The key is then used to generate a SAS token, which the client uses to authenticate with the Service Bus.

  • Access Control Service (ACS): This provides identity federation with various providers. To access the Service Bus entities, the client requests a Simple Web Token (SWT) from the ACS. The token is then sent with every request to the Service Bus.

While creating a Service Bus Queue using the Azure Portal, the only available authentication...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image