Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Azure Stack Hub Demystified

You're reading from  Azure Stack Hub Demystified

Product type Book
Published in Oct 2021
Publisher Packt
ISBN-13 9781801078603
Pages 414 pages
Edition 1st Edition
Languages
Author (1):
Richard Young Richard Young
Profile icon Richard Young

Table of Contents (21) Chapters

Preface 1. Section 1: Architecture and Deployment
2. Chapter 1: What Is Azure Stack Hub? 3. Chapter 2: Azure Stack Architecture 4. Chapter 3: Azure Stack Hub Deployment 5. Section 2: Identity and Security
6. Chapter 4: Exploring Azure Stack Hub Identity 7. Chapter 5: Securing Your Azure Stack Hub Instance 8. Chapter 6: Considering DevOps in Azure Stack Hub 9. Section 3: Features
10. Chapter 7: Working with Resource Manager Templates 11. Chapter 8: Working with Offers, Plans, and Quotas 12. Chapter 9: Realizing Azure Marketplace 13. Chapter 10: Interpreting Virtual Networking 14. Chapter 11: Grasping Storage and Compute Fundamentals 15. Section 4: Monitoring, Licensing, and Billing
16. Chapter 12: Monitoring and Managing Azure Stack Hub 17. Chapter 13: Licensing Models in Azure Stack Hub 18. Chapter 14: Incorporating Billing Models 19. Chapter 15: Troubleshooting and Support 20. Other Books You May Enjoy

Understanding the Azure identity model

Microsoft Azure Stack Hub uses identity at different layers. This includes portals and tools that sit on top of Azure Resource Manager (ARM). Moving further down the stack, we also use identity for resource providers. We also use identity for business logic and infrastructure, as shown in the following diagram:

Figure 4.1 – Azure identity layers

As you can see from this diagram, the tokens and access tokens used across the layers are different depending on which layer of Azure Stack Hub we are talking to.

For applications and users, the architecture of Azure Stack Hub is broken down into four layers, as shown in the preceding diagram. Interactions between these layers can use different types of authentication.

For tools and clients such as the administrator portal, the authentication used to communicate to the ARM is via a JSON Web Token. ARM validates the JSON Web Token and looks at the claims issued in the...

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 $15.99/month. Cancel anytime}