|
You are here |
www.primaryobjects.com | ||
| | | | |
michaelscodingspot.com
|
|
| | | | | Michael Shpilt's Blog on .NET software development, C#, performance, debugging, and programming productivity | |
| | | | |
brockallen.com
|
|
| | | | | There have been many changes to how authentication is performed for web applications in Visual Studio 2013. For one, there's a new "Change Authentication" wizard to configure the various ways an application can authenticate users. The approach to authentication that's undergone the most changes in this version is local cookie-based authentication and external login providers... | |
| | | | |
www.adamalbrecht.com
|
|
| | | | | UPDATE: There have been some changes in the JWT Gem that make some of the below not work exactly right (it'll still be about 90% the same). Specifically, they added expiration support. See my post on the same topic, but using React.js. The server side code in this post will work just as well with Angular. | |
| | | | |
www.inogic.com
|
|
| | | Introduction: In our recent blog, We saw how to create an Azure function and now that we have our Azure function ready and hosted, let's look at invoking the function through a workflow. At this point, we will execute the function through an HTTP request instead of registering the function as a Webhook. Let us modify the | ||