Okta is a cloud service that allows developers to create, edit, and securely store user accounts and user account data, and connect them with one or multiple applications. NET app to Azure? Well, you wouldn’t mail a letter without sealing the envelope, would you? Similarly, you shouldn’t ship your new app out to the Internet without secure identity management, and Okta makes that a lot easier and more scalable than what you’re probably used to. Why does Okta matter if this post is all about deploying my. In this tutorial we’ll add secure identity management to your ASP.NET Core app with Okta, and then deploy to Azure. My method might not be as fast as right clicking to publish, but it’ll keep you, and your users, safe! (And if you’re embracing the cross-platform nature of ASP.NET Core, like I am on my Linux laptop with VS Code, right-click to publish isn’t even an option for you.) In this post I’ll walk you through the right way to secure and deploy your new ASP.NET Core app to Azure. There are very few instances in which you’d actually want to make use of this “feature” and so many more in which it’s a terrible idea. One of the scariest features of Visual Studio is without a doubt right-click to publish.
