Explore >> Select a destination
|
You are here 
|
dylanbeattie.net | ||
| | | | |
damienbod.com
|
|
| | | | | The article shows how to implement user management for an ASP.NET Core application using ASP.NET Core Identity. The application uses custom claims, which need to be added to the user identity after a successful login, and then an ASP.NET Core policy is used to authorize the identity. Code: https://github.com/damienbod/AspNetCoreAngularSignalRSecurity History 2023-01-07 Updated .NET 7, Angular... | |
| | | | |
sandrino.dev
|
|
| | | | | An introduction on how to configure JWT Bearer authentication and authorization (based on scopes) for your ASP.NET Core 5 APIs. | |
| | | | |
jamiemaguire.net
|
|
| | | | | In the previous blog post, we saw how to use logging to examine planners and help debug your Semantic Kernel solution. In this blog post, you will see how to expose the customer service agent we've been building in a custom webchat experience using ASP.NET Core. This blog ties together many of the concepts from earlier posts and demos. All previous posts in the series can be found here: First Look, Integrating Semantic Kernel with Open AI (Part 0) - An introduction to Semantic Kernel, who is it for, why ... | |
| | | | |
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 | ||
