ASP.Net Core 2.0 came out recently and there were quite a few changes to the
authentication scheme. In this article, I’ll talk about how to setup token based authentication using JWT’s in ASP.Net Core 2.0. We’ll use the Identity system to handle authentication, and Entity Framework to access an MS SQL backend. NOTE: you will probably need to install the .Net Core 2.0 Libraries.
The source code for this can be found here. Continue reading “Token Based Authentication Using Asp.Net Core 2.0”
In Part 1 we setup basic token authentication using JWT’s with asp.net. Things are setup reasonably but all is not well. As a developer, you could give the token a lifespan of 30 days and just force the user to re-login after those days but what if you make the user inactive and don’t want him to login anymore? There must be better way.
Generally, I token has a lifetime of about an hour and when it expires, we want to refresh that token, verifying that the user still has access to the system, etc. The method that this is handled is using refresh tokens. A refresh token is returned along with the normal token and it’s stored for when we must refresh normal token.
Starting from our previous app, let’s support refresh tokens. Note, the completed code for this blog can be found here.
This will require us to track refresh tokens in our database, so first, let’s create the RefreshToken model.
Jeff Jorgensen has been a valuable member of the IBS family since 2001. Starting out as the Cincinnati branch manager and working his way to becoming President of the company in 2015, Jeff is responsible for much of IBS’ success. We sat down with him to learn more about his experience at IBS and to find out what he’s like outside of the office.
Where did you go to college and what did you study?
I went to Kent State University and double majored in Accounting and Finance. When I had to depreciate a leased asset, I realized that I may need to do something other than accounting!
Continue reading “The IBS Longtimers: An Interview with Jeff Jorgensen”
A couple weeks ago, Microsoft held their annual Ignite conference and I would usually be blogging about all the cool new things coming to Office 365. This year has been a bit a different experience altogether, not for a lack of features announced from Microsoft though…there were plenty of awesome new features announced. We’ve spent the past couple weeks fielding questions on Office 365 from existing customers and folks looking to make the move or at least understand the options available.
Continue reading “Office 365 Collaboration Confusion”
This afternoon I’m leading a Lunch & Learn at IBS friend and client Total Quality Logistics. I’ll be teaching them everything I know about Angular 2 and how we’ve utilized it in projects over the past few months. Should be a lot of fun! I’ll follow up later today with more details on how the event went.
If YOU are interested in having me or someone else from Nerdia (aka the IBS Mobile & Web Solutions Group) come for lunch to teach your team about Angular 2, Git, SharePoint and more, fill out the form here.
The front-end testing I’ve done in the past has always had some friction with respect to getting the tools setup properly. Mostly I have used Jasmine as the testing framework, which is pretty self contained – but to get a node test server setup properly there are a variety of other npm modules and karma configuration settings to deal with. I previously wrote about how the angular-cli makes it easy to get an Angular 2 project setup, and this includes getting the test tools setup as well. So instead of dealing with configuration settings, you can quickly get to just writing tests.
Continue reading “Angular 2 – Testing”
One of the good things about Angular 1 was that it was easy to add the AngularJS library to your application and start using it without a lot of setup ceremony. Add a <script> tag to pull in angular.js, stick an ng-app attribute on the body or html tag, and you were ready to go. Of course, in a more complex application you would end up using additional libraries and probably setup a build process, but the barrier to getting started was low.
With Angular 2, getting started from scratch is not nearly as simple. While there are multiple “starter-packs” that have been created to help with generating a ready-to-go project, the thing that has most caught my attention is the Angular CLI (command-line-interface). Although the Angular CLI has not been officially released (it is in beta as of this writing), it already has a number of features that not only get you up and running quickly, they also help with adding other pieces of your application as it is developed.
Continue reading “Angular 2 CLI”