Search icon CANCEL
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
Learning Microsoft Azure

You're reading from   Learning Microsoft Azure A comprehensive guide to cloud application development using Microsoft Azure

Arrow left icon
Product type Paperback
Published in Oct 2014
Publisher Packt
ISBN-13 9781782173373
Length 430 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Geoff Webber Cross Geoff Webber Cross
Author Profile Icon Geoff Webber Cross
Geoff Webber Cross
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Getting Started with Microsoft Azure FREE CHAPTER 2. Designing a System for Microsoft Azure 3. Starting to Develop with Microsoft Azure 4. Creating and Managing a Windows Azure SQL Server Database 5. Building Azure MVC Websites 6. Azure Website Diagnostics and Debugging 7. Azure Service Bus Topic Integration 8. Building Worker Roles 9. Cloud Service Diagnostics, Debugging, and Configuration 10. Web API and Client Integration 11. Integrating a Mobile Application Using Mobile Services 12. Preparing an Azure System for Production Index

Answers

  1. SQL Azure only supports SQL authentication, which means that the client application needs access to the login details, which can pose a security risk.
  2. SignalR clients maintain connections to a single hub, which means that they will not send data to or receive data from other hub instances.
  3. Implement a backplane system such as Azure Service Bus to keep hubs updated in real time.
  4. Use the Authorize attribute at the controller or individual action level.
  5. If we temporarily remove the Authorize attribute, we can use the browser to make HTTP GET requests or a tool such as Fiddler or cURL to make other requests.
  6. The hub SignalR URL is api/signalr.
  7. We use the same Authorize attribute.
  8. An AD application will be provisioned for the new site and the site's Web.config file will be updated with the new ida:Audience ID.
  9. Client applications need to be given permission to access them.
  10. The ida:Audience ID is the ID of the target application, that is, the Web API, and ida:ClientID is the ID of the client...
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