Explore >> Select a destination
|
You are here 
|
blog.hboeck.de | ||
| | | | |
tool-box.info
|
|
| | | | | ||
| | | | |
sergioprado.blog
|
|
| | | | | This article is going to be an introduction to embedded Linux security. | |
| | | | |
daniel-lange.com
|
|
| | | | | ||
| | | | |
svrooij.io
|
|
| | | I'm super enthusiastic about managed identities, because it allows you to deploy your application without having to worry about credentials. Federated credentials are a way to accomplish the same for none Azure resources. You can use federated credentials to authenticate several tasks inside Github Actions, and thus securely deploy your app to Azure without the need of a secret configured in GitHub. As the regular readers might expect this post will explain how federated credentials actually work inside GitHub Actions, a deep dive into the techniques that are actually driving this feature. Get a federation token from GitHub | ||
