Abstract
Sooner than later, a service will have to use one or more secrets to access other systems – whether it is an API key, a password, or something sensitive. In this chapter, you will learn what challenges the secrets impose on your applications and what are the bad practices that you have to stay away from. After a short introduction about what secret managers are and what benefits they bring to the table, you will learn how Dapr simplifies the retrieval of secrets with the Secrets building block. Next, you will learn what secret stores are supported and how you can access them by either referencing secrets right in the Dapr component manifests or by calling the Secrets API from your services. Later, you will see how easy it is to use Kubernetes Secrets and how to use Azure Key Vault if you want to back away from using solely relying on Kubernetes. To wrap up the chapter, I will show you how you can control the access of Dapr applications to secrets.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2021 The Author(s), under exclusive license to APress Media, LLC, part of Springer Nature
About this chapter
Cite this chapter
Gatev, R. (2021). Secrets. In: Introducing Distributed Application Runtime (Dapr). Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-6998-5_11
Download citation
DOI: https://doi.org/10.1007/978-1-4842-6998-5_11
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-6997-8
Online ISBN: 978-1-4842-6998-5
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)